Basic frontend collection management

[jgonggrijp]

While frontend collection handling forms the overarching story of this branch, it is a bit of a hodgepodge of small changes:

• Fixed #224 (restores ability to list and display collections).
  • Adjusted existing models, views and other parts to the changed field names.
  • Changed the project menu to automatically switch to the project of the current collection, since each collection can now be associated with only one project.
  • Made the summary of a collection visible through a <small> insertion in the page header.
  • Abolished the conceptual difference between "my collections" and "all collections", because the backend endpoint will never list collections beyond the ones the user has access to.
  • Set the idAttribute of the Backbone model that represents a single VRE collection to uri.
• Minimally implemented #225 (create and partial update only).
  • Added an inline form to the bottom of the collection menu that lets the user quickly whip up new empty collections.
  • Added an inline form that can be temporarily overlaid over the <small> in the page header in order to adjust the summary of a collection.
    • Created a separate, generic, reusable OverlayView in order to support this. It can do one thing: temporarily replace an arbitrary DOM element by an arbitrary view, based on a selector relative to a persistent root element.
• Other fixes, refactorings, cosmetic changes and enhancements (mostly just to give myself an easier time while working on the above changes).
  • Enabled alt-click debugging for all views (with the exception of views that aren't reachable by mouse, such as OverlayView instances).
  • Set the idAttribute of the Project model to name. It appears that the idAttribute was never set to a correct value before this.
  • Added an .editorconfig.
  • Added temporary files generated by emacs (which I use) to the .gitignore.
  • Renamed the "annotation context" menu to just "project", because I felt this conveys the meaning of the menu better.
  • Wrote "Collection" instead of "Browse or search" in the header of the collection page, because I think this signals more clearly to the user what they are viewing.
  • Added a provisional auto dark mode.
  • Removed headlessChrome from the default browsers in the Karma config as discussed in https://github.com/UUDigitalHumanitieslab/EDPOP/pull/200#discussion_r1740803381.
  • Removed the project menu and associated collections from the GlobalVariables, using the vreChannel instead for loose coupling. This brings us a bit closer to #123 again.
  • Replaced the old, simple but faulty logic for appending trailing slashes to model URLs by the more sophisticated and thoroughly tested modelSlashUrl from backbone-util.

I will be on vacation soon, so I prioritized fast delivery over comprehensiveness. Hence, there are some omissions and rough edges that I am aware of:

• Collections cannot be deleted. I think this should eventually be possible, but it needs to be designed carefully to minimize the risk that users accidentally lose a lot of work.
• The name of a collection cannot be changed. I opted out of this because I did not want the name and the uri to diverge. In the future, users could conceivably work around this by adding all records from one collection to another and then deleting the source collection.
• A project must be selected before you can create a collection. If no project is selected, collection creation silently fails, but an entry with the new name still appears in the menu.
• There is no validation or error handing for the create and update actions.

There are also things that were already broken on develop and which are not fixed by this branch:

• Collections created before #181 are not visible because of #226.
• There is no way to add or list records in collections because the records endpoint still has to be updated.
• Project selection should probably be more prominent.

For review, I suggest giving the frontend a quick spin and just scrolling through the code changes. There are lots of files with only minor changes, but I think you will be able to quickly identify repeating patterns and skip over those.

[tijmenbaarda]

• A project must be selected before you can create a collection. If no project is selected, collection creation silently fails, but an entry with the new name still appears in the menu.

When I try this, no new entry is added to the menu but an exception project is undefined is raised.