Project update view cannot be used with deactivated catalogs

According to the recommendation of deactivating old catalogs and importing new versions in addition, user might still want to change the description of existing project. Navigating from the project details these settings are seperated into three views: (1) for the update of title and description, (2) for the update of the underlying catalog, and (3) for the update of the parent project. However in the project overview this is in a single form (/projects/id/update/) which results in the situation that users cannot submit changes if the catalog is no longer available (in favor of a new version).

A solution that corresponds with this catalog update strategy might be to remove the extended project update view and link the three separate views.

Start by tracing the project overview form at /projects//update/ and compare it with the three separate views for title and description, catalog, and parent project updates. Confirm how a deactivated catalog prevents submission, then separate or link these update paths so description changes remain possible without the unavailable catalog; verify the affected project update flows.