update_application_forms

Put forms into an application, or take them out. Use get_application_details to see what is in it now.

An application does not own its forms. A form can belong to several applications at once, and a form belonging to none still works and is still reachable by anyone whose permissions allow it. So this changes how a form is found, not whether it exists or who may use it.

This takes forms to add and forms to remove rather than a complete list of what the application should contain, which is the opposite of update_form, where a form states all of its applications at once. The asymmetry is deliberate: a form belongs to few applications, so listing them all is bounded, whereas an application can hold many forms and a complete list supplied from memory would quietly drop anything missed by mistake.

Menu items follow the form. Taking a form out of an application moves its menu items to wherever the form went - to another application if you are adding it to one, or to the “forms with no application” area if it now belongs to none.