Separate REST API endpoints from Web UI API

We keep running into issues with the API endpoints changing and the OpenAPI spec getting outdated.

Instead of trying to use the same API for integrations and to support the frontend I propose we could separate the REST API meant for automations/scripts/integrations into a dedicated namespace (probably current /api/v1) with completely separate structs (and possibly a separate crate in the future) etc.

This API would stay mostly static and have full Swagger documentation. It should probably just reflect the DB models as a starting points and not our compound structs which are necessary to service specific frontend needs.

Then the webapp could have a completely separate API which we could do whatever with and not worry about breaking compatibility or updating the docs.