Refactor accessing Ruuter DSLs

[turnerrainer]

Background

• All Ruuter DSLs meant to be directly accessible are called Service Endpoints in scope of this task
• All Ruuter DSLs needed to serve Service Endpoints are called Internal Endpoints in scope of this task

AS AN Architect
I WANT Ruuter DSLs to be structured and thereby accessible based on their type (Service vs Internal Endpoints)
SO THAT service DSLs would be separated from internal DSLs

Acceptance Criteria

• Apply RESTful naming convention on all Service Endpoints

For example, /chat-init and /end-chat should instead be accessible via /chat/init and /chat/end

• Move all Internal Endpoints into a sub-folder called internal of their respective Service Endpoint

For example, /chat/init would use /internal/chat/message-to-bot for its internal requests

• All user authentication must be done via template Ruuter DSLs

See this as an example calling out templated user authentication

Prerequisites

• Based on Allowlist of Ruuter services exposed as public REST endpoints Ruuter#158

Scope

• All developments will be done within ruuter-sidecars branch until ready
• When done, all developments will be merged from ruuter-sidecars to dev branch

Ruuter

• https://github.com/buerokratt/Buerokratt-DSL/tree/ruuter-sidecars/Ruuter

Backoffice

• https://github.com/buerokratt/Buerokratt-Chatbot/tree/ruuter-sidecars

Chat Widget

• https://github.com/buerokratt/Chat-Widget/tree/ruuter-sidecars

[turnerrainer]

Reopen to deploy after latest PRs.

[turnerrainer]

Needs further attention based on buerokratt/Ruuter#293