"view" doesn't change when "catalog" is changed

[RH-DIPF]

Description / Beschreibung

Changing a catalog of a project does not automatically update the list of views that are associated with that catalog.

Expected behaviour / Erwartetes Verhalten

Changing a catalog of a project automatically updates the list of views that are associated with that catalog.

Steps to reproduce / Schritte zum Reproduzieren

1. A new project is created by a user.
2. The user selects "catalog A" which as a view ("View A") associated with it.
3. Then the users switches in the same project the catalog from "catalog A" to "catalog B". "catalog B" has it's own view ("View B") associated with it.
4. But the view that the users sees never switches. He still just sees "view A" even after switching to catalog B.

Context / Kontext

If the users switches to a catalog without any views, he doesn't see any views anymore.
This is apperently an old issue #345 that was merged with an other issue #431 . But the bug from #345 was never really resolved.

[jochenklar]

Hi @RH-DIPF @m6121, since views are in principle independent from catalogs, we let projects choose, which views are used in the project. This collides with the feature that views have a catalog field (which was added later) and I see that a lot of people now have the requirement that the views are more or less strictly connected to a catalog and not to the project. The same holds for tasks, but people seem to be less interested in tasks ...

We already have the feature flag PROJECT_REMOVE_VIEWS for the feature that @m6121 implemented. Maybe we should rename it to PROJECT_VIEWS_SYNC to indicate that this instance keeps the views of a project in sync with the catalog. We could also remove the possibility to choose the views freely in this case. Otherwise people could select additional views, which are then removed, when the catalog is changed or updated.