Add meta menu to forms

[maxpatiiuk]

For controlling things like:

• Carry forward (Allow configuring carry forward in forms #1793)
• Autonumbering (Allow enabling auto numbering on field by field basis #1794)
• Whether default or custom form is used
• A button to see the history of changes for a record (Add an easy way to see the edit history for a record #1703)
• For Collection Objects, a button to copy a link to current record (where the link is in the /specify/bycatnum/<collectionCode>/<catNum>/ format, rather than by ID)
• For tree records, add a button to see associated collection objects: (Add easier way to view Collection Objects associated with a tree node #1728)
• For SubViews, add an option to change the sort order
• For SubViews, add an option to toggle between grid and form view (One to many tables can no longer switch between being displayed as grid or subform on the form #1723)
• For pick lists, a way to see which fields the pick list is used by
• A button to go to form definition
• A switch to temporary disable field labels (Add a switch to temporary disable field labels #1581)
• "Generate Label on Save" checkbox (it doesn't really belong on the form, since it does not edit the record, and is not specific to a given record)
• A button to create a label/report from the record ([testability] Include "Generate Invoice" button in the FormMeta menu #1996)

[maxpatiiuk]

The link to form definition currently assumes that the view definition is coming from collection's view set.

The /context/view.json?name=Taxon endpoint provides correct view set location. Front-end needs to listen to it

[grantfitzsimmons]

Looks good to me. This is very broad, so issues that occur from this change should be addressed independently in my opinion. Please reopen if there is more to this that needs discussion.