Fix mermaid console errors

[paulbrimicombe]

🧐 What?

Currently when a Mermaid diagram is included in the page the following errors can be seen in the console:

Uncaught ReferenceError: mermaid is not defined
Uncaught TypeError: Cannot read properties of undefined (reading 'mermaid')

Screenshot:

This is because the mermaid.min.js bundle is imported as an ES Module (using type="module") but it is expecting to be imported as a "classic script". When imported as a module, the mermaid global object fails to be set and the mermaid bundle throws an error. All diagrams still render successfully, however.

An ESM version of Mermaid does exist but is difficult to use because:

• The NPM package does not include a single-file ESM bundle — it's split across multiple files which would all need to be uploaded to S3
• The CDN distribution does have a single-file ESM bundle but using this makes version management more difficult than using the NPM package (and would mean that tools like dependabot wouldn't be able to monitor vulnerabilities for the Mermaid dependency).

🛠 How

Removing the type attribute from the Mermaid <script> tag eliminates the console errors