New features

Possibility to add permission checks for tags and collections
- IF YOU ARE NOT USING PERMISSIONS: The collections can only be managed by the collection owner and moderators. Separate read and edit access to collections have been removed. Tag creation will work based on the configuration flag qeta.tags.allowCreation and is true by default like previously
- IF YOU ARE USING PERMISSIONS: Tags cannot be any more updated by anyone. If you want to enable this, add a new permission check, example here. Additionally, you must allow reading tags and collections in your permission policy accoringly.
- There are a few available rules for each permission, check those out from here
New QetaSearchResultListItem is exported from @drodil/backstage-plugin-qeta that can be used to show search results in more beautiful way. See https://github.com/drodil/backstage-plugin-qeta/blob/main/docs/search.md for more information
Q&A home plugin table can now show also articles. In customizable home page this can be selected by the user or this can be passed also as a prop to PostsTableCard component

Improvements

Permission rules and conditions have been moved to @drodil/backstage-plugin-qeta-node package. The backend package exports these as deprecated and they will be removed in a future release.
As the loading times can get higher due to permission checks, there are now better loading indicators for each page
A couple of navigation and rendering improvements all over the UI
Comments are now stored in one table instead of separate ones for posts and answers. The existing data will be migrated automatically