* main: (213 commits)
website/docs: configuration: fix typo in kubectl command (#10492)
website/integrations: fix typo in minio instructions (#10500)
web: bump @typescript-eslint/eslint-plugin from 7.5.0 to 7.16.0 in /tests/wdio (#10496)
website: bump prettier from 3.3.2 to 3.3.3 in /website (#10493)
core: bump ruff from 0.5.1 to 0.5.2 (#10494)
web: bump @typescript-eslint/parser from 7.5.0 to 7.16.0 in /tests/wdio (#10495)
web: bump eslint-plugin-sonarjs from 0.25.1 to 1.0.3 in /tests/wdio (#10498)
web: bump prettier from 3.3.2 to 3.3.3 in /tests/wdio (#10497)
web: bump pseudolocale from 2.0.0 to 2.1.0 in /web (#10499)
core: bump goauthentik.io/api/v3 from 3.2024061.1 to 3.2024061.2 (#10491)
web: bump API Client version (#10488)
flows: remove stage challenge type (#10476)
core: bump github.com/redis/go-redis/v9 from 9.5.3 to 9.5.4 (#10469)
core: bump goauthentik.io/api/v3 from 3.2024060.6 to 3.2024061.1 (#10470)
web: bump the babel group across 1 directory with 2 updates (#10471)
web: bump the storybook group across 1 directory with 7 updates (#10472)
core: bump coverage from 7.5.4 to 7.6.0 (#10473)
website/docs: air gapped: clarify .env usage at the top for Kubernetes installations (#10447)
website/docs: air gapped: update "see configuration" wording (#10448)
website/docs: Add Kubernetes Bootstrap Instructions (#9541)
...
This commit adds HTMLTagNameElementMap entries to every web component in the front end. Activating
and associating the HTMLTagNamElementMap with its class has enabled
[LitAnalyzer](https://github.com/runem/lit-analyzer/tree/master/packages/lit-analyzer) to reveal a
*lot* of basic problems within the UI, the most popular of which is "missing import." We usually get
away with it because the object being imported was already registered with the browser elsewhere,
but it still surprises me that we haven't gotten any complaints over things like:
```
./src/flow/stages/base.ts
Missing import for <ak-form-static>
96: <ak-form-static
no-missing-import
```
Given how early and fundamental that seems to be in our code, I'd have expected to hear _something_
about it.
I have not enabled most of the possible checks because, well, there are just a ton of warnings when
I do. I'd like to get in and fix those.
Aside from this, I have also _removed_ `customElement` declarations from anything declared as an
`abstract class`. It makes no sense to try and instantiate something that cannot, by definition, be
instantiated. If the class is capable of running on its own, it's not abstract, it just needs to be
overridden in child classes. Before removing the declaration I did check to make sure no other
piece of code was even *trying* to instantiate it, and so far I have detected no failures. Those
elements were:
- elements/forms/Form.ts
- element-/wizard/WizardFormPage.ts
The one that blows my mind, though, is this:
```
src/elements/forms/ProxyForm.ts
6-@customElement("ak-proxy-form")
7:export abstract class ProxyForm extends Form<unknown> {
```
Which, despite being `abstract`, is somehow instantiable?
```
src/admin/outposts/ServiceConnectionListPage.ts: <ak-proxy-form
src/admin/providers/ProviderListPage.ts: <ak-proxy-form
src/admin/sources/SourceWizard.ts: <ak-proxy-form
src/admin/sources/SourceListPage.ts: <ak-proxy-form
src/admin/providers/ProviderWizard.ts: <ak-proxy-form type=${type.component}></ak-proxy-form>
src/admin/stages/StageListPage.ts: <ak-proxy-form
```
I've made a note to investigate.
I've started a new folder where all of my one-off tools for *how* a certain PR was run. It has a
README describing what it's for, and the first tool, `add-htmlelementtagnamemaps-to-everything`, is
its first entry. That tool is also documented internally.
``` Gilbert & Sullivan
I've got a little list,
I've got a little list,
Of all the code that would never be missed,
The duplicate code of cute-and-paste,
The weak abstractions that lead to waste,
The embedded templates-- you get the gist,
There ain't none of 'em that will ever be missed,
And that's why I've got them on my list!
```
