Add / import <mapml-viewer> to gcds under components/gcds-map

[prushforth]

Add dependency on @maps4html/mapml

Update stencil config to copy mapml to dist output directory.

Update index.html with example <mapml-viewer>

Add gcds-map.stories.tsx

Make mapml a dependency, not a devDependency, since it must be present
at runtime / installed with product

Add dist/gcds/gcds-map as static resource directory for storybook.

Change how controls is implemented by stencil to make it consistent
with boolean attribute with default of false when not present

Make controlslist a multi-select in storybook

Make gcds-map a component only in name, created for the purpose of
importing the map client CSS rules in gcds-map.css.

Add global script to dynamically and conditionally import mapml.js;
global script can refer to other global script imports as required.

Include very basic gcds-map.css in build, integrate via run time load

Add mapml.js and gcds-map.css imports to storybook preview-head.html,
so that it appears in the iframe regardless of whether the <mapml-viewer>
has been rendered yet.

Add some basemap mapml (services) directory contents to component definition
for use in index.html and storybook

Co-authored-by: Pierre Dubois <[email protected]>

Summary | Résumé

1-3 sentence description of the changed you're proposing, including a link to
a GitHub Issue # or Trello card if applicable.

---

Description en 1 à 3 phrases de la modification proposée, avec un lien vers le
problème (« issue ») GitHub ou la fiche Trello, le cas échéant.

Test instructions | Instructions pour tester la modification

Sequential steps (1., 2., 3., ...) that describe how to test this change. This
will help a developer test things out without too much detective work. Also,
include any environmental setup steps that aren't in the normal README steps
and/or any time-based elements that this requires.

---

Étapes consécutives (1., 2., 3., …) qui décrivent la façon de tester la
modification. Elles aideront les développeurs à faire des tests sans avoir à
jouer au détective. Veuillez aussi inclure toutes les étapes de configuration
de l’environnement qui ne font pas partie des étapes normales dans le fichier
README et tout élément temporel requis.

[prushforth]

I was testing how it would work in a released form (had only run it inside the project dev environment up to now) and I realized that the path to the mapml.js module was dependent on the dev configuration. So I updated that just now, and it "should work" in an installed environment with this update. Thanks for your review, happy to meet and discuss together, to see if there's more I can do to make it easy to integrate into the next release or so. PR

[prushforth]

Closes #773

[daine]

@prushforth thanks for this PR, really appreciate it, and I added a comment to the issue you have opened as well. I'm hoping to have some time next week to start the review, and I can email or message you soon once we have a better sense of the scope of work.