docs: update element references from pf-* to pf-v5-*

Update all docs site references to use the new pf-v5-* element names,
including HTML tags, CSS selectors, import paths, and code examples.

Blog posts and changelogs left unchanged as historical records.
PF4 core CSS tokens (--pf-c-content/title/text) left unchanged as
they reference the PF CSS framework, not pf-elements components.

Assisted-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: bennypowers

docs/get-started.md

@@ -47,16 +47,11 @@ title: Get started
   In this example, we load the [card](/components/card/) modules using an importmap from JSPM.
 
   ```html
-  <script type="importmap">
-  {
-    "imports": {
-      "@patternfly/elements/": "https://ga.jspm.io/npm:@patternfly/elements/"
-    }
-  }
-  </script>
+  {% generateImportMap %}
   <script type="module">
     import "@patternfly/elements/pf-v5-card/pf-v5-card.js";
   </script>
+  {% endgenerateImportMap %}
   ```
 
   To learn more about how to create importmaps, read our [creating an import map](/docs/develop/import-maps/) section, and go into more detail at [developer.mozilla.org](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/script/type/importmap) or the [import map specification](https://html.spec.whatwg.org/multipage/webappapis.html#import-maps).