Feature/algolia v14

[acoumb]

Current PR contains the updates for Umbraco 14 for Algolia integration, with some bugfixes and design updates.

This is also to get feedback on the release-ready status of the integration based on your experience with the other products.

[acoumb]

Fixed api resources generation by using the Swagger JSON schema on http instead of https, and updated all references.

[nathanwoulfe]

Looks like I've made a stack of changes, but most of it is just linting/style to align with the other products.

• I've updated the API controllers to remove the protected properties on the base controller and instead have each controller provide its own dependencies - slims down the controllers as they only deal with direct concerns.
• found my stack overflow issue from yesterday - GetContentTypesController had an endpoint method named GetContentTypes and a private method with the same name accepting an optional int ID argument. Former attempted to call the later, but fell into a self-referencing loop. Renamed a couple of methods and we're all good.
• added the eslint rules used in other projects, which I originally stole from CMS, again just for consistency
• moved generated files from /src/api to /generated, again just for consistency

Couple of remaining things to consider:

• do we need a context at all? The dashboard element could directly new up a repository and away we go. Context isn't storing any stateful data, but I suppose it's going to be more performant to not init the repo and data-source on every route event.
• given the above, if we keep the context we could remove the data-source and have the repo call the services directly. Repo-datasource-store pattern is useful, but we don't have to use it if we don't get any benefit from it
• would be good to look at moving the error handling down to the repository layer (rather than the dashboard/views) as we can then manage error notifications in the repo, and provide only data back to the views, which would simplify these quite a bit, eg:

  await this.#algoliaIndexContext?.getIndices()
          .then(response => {
              this._indices = response as Array<IndexConfigurationModel>;
              this._loading = false;
          })
          .catch(error => this.#showError(error.message));

  can use async/await without the callbacks:

  this._indices = await this.#algoliaIndexContext?.getIndices();
  this._loading = false;

Long story short, this is looking great and ready to go (things to consider above can be done at any time, if we want to)

[acoumb]

@nathanwoulfe I've removed the data source and moved the logic and error handling to the repository scope. Also I made some small fixes along the way. Could you have a quick look over things now before merging them? Thank you.

[nathanwoulfe]

@acoumb looks good to me - I made a couple more changes

• use type for context rather than the element reference (means one fewer import)
• de-structure the response from the repository (means one fewer variable each call)
• mainly because I wanted to see if it was possible, the selected content types and properties are now highlighted on load.
• use umb-property-layout rather than the form layout, it is styled better for the backoffice