Provide various improvements to the module

Problem/Motivation

There are a few features that'd be nice to be implemented in the module.
So I have decided to integrate them here as a single issue rather than create lots of separate issues:

• Provide a config schema to describe the data structure of the Block configuration.
• Provide better support for working with relative URLs (passing the current query strings into the request, and provide a way to automatically specify the initialDate if the "start" query is specified in the URL, and supporting multilingual installations)
• Remove trailing ' in the fullcalendar-block.html.twig template
• Provide a way to switch to the non-minified version of Fullcalendar assets during development.
• Expand the libraries.yml into separate declarations so that the Drupal javascript can be properly cache busted rather than have a static version of "?v=5.10.2".
• Add the option to open events in the current tab
• Since YAML is a superset of JSON, way more human friendly to use and fits well with the Drupal ecosystem, we can safely switch to using YAML for the advanced settings instead - https://yaml.org/spec/1.2/spec.html#id2759572
• Piggy back off other YAML editors if they exist to provide a better editing experience.
• Add better integration for jquery_ui_draggable and jquery_ui_resizable if they're installed.
• Add support for rendering a special details field in the dialog if it exists (same as in fullcalendar_view).
• Add support for better localization by fetching it from the current Drupal installation - setting the first day, direction and locale.

Steps to reproduce

N/A

Proposed resolution

Address issues.

Remaining tasks

Provide issue fork/patch.

User interface changes

• There's now a new "Advanced Drupal settings" field which can be used to pass advanced configurations for the dialog such as which custom field to use for the dialog popup, defaults to des by default
• If the site has codemirror_editor, webform or yaml_editor installed, it'll attempt to use them to edit the advanced JSON/YAML configurations

API changes

drupalSettings.fullCalendarBlock[blockIndex].calendar_options is now an object rather than a string to make it easier for contrib modules and other Javascript to work with and manipulate.

The blockIndex is no longer a numeric ID based since it doesn't work well with Drupal cache when multiple blocks are rendered on the same page, or rendered in different ways e.g. Panels or Layout Builder. The ID is now a unique string similar to how Views' dom_id works.

Switch the DOM attribute from calendar-block-index to data-calendar-block-index since the former results in invalid HTML.

Provide access to the individual block instances under the Drupal.fullcalendar_block.instances property.

Data model changes

N/A