chore(jans-config-api): document ADS projects management endpoint

[jgomer2001]

Recently I added the endpoints related to ADS projects, see #3094

These lack the swagger stuff, please add them

Soon I'll be posting here details about how these endpoints are used

[jgomer2001]

All URLs are relative to /jans-config-api/api/v1

Endpoint ->	/ads-deployment/list
Purpose	Retrieve a list of deployments in the server. This is not a search, just a paged listing
Method	GET
Query params	start and count helps paginating results. start is 0-index based. Both params optional
Output	Existing deployments (regardless they are thoroughly processed or still being deployed). They are listed and sorted by deployment date
Sample output	{"start":...,"totalEntriesCount":...,"entriesCount":...,"entries":[ ... ]}
Status	200 (OK)

Endpoint ->	/ads-deployment
Purpose	Retrieve details of a single deployment by name
Method	GET
Query params	name - mandatory
Sample output	The structure of a deployment is explained below
Status	200 (deployment task is finished), 204 (task still in course), 404 (project unknown), 400 (a param is missing)

Deployment structure	Notes	Example
dn	Distinguished name	jansId=123,ou=deployments,ou=agama,o=jans
id	Identifier of deployment (generated automatically)	115276
createdAt	Datetime (in UTC) of the instant the deployment task was created (POSTed)	2022-12-07T21:47:42
taskActive	Boolean value indicating if the deployment task is being currently processed, ie. the .agama file is being scanned, flows analysed, etc.	false
finishedAt	Datetime (in UTC) representing the instant when the deployment task was finished, or null if it hasn't ended	2022-12-07T21:48:42
details	Extra details, see below

Deployment details structure	Notes	Example
projectMetadata	Includes author, type, description, and project's name - as supplied when the deployment task was created	Ref bean here
error	A general description of the error (if presented) when processing the task, otherwise null	Archive missing web and/or code subdirectories
flowsError	A mapping of the errors obtained per flow found in the archive. The keys correspond to qualified names. A null value indicates the flow was successfully added	{ "co.acme.example": "Syntax error on line 4", "io.jans.test": null }

Endpoint ->	/ads-deployment
Purpose	Add or replace an ADS project to the server
Method	POST
Query params	name (the project's name) - mandatory
Body	The binary contents of a .gama file. See example below. Ensure to use header Content-Type: application/zip
Output	Textual explanation, e.g. A deployment task for project XXX has been queued. Use the GET endpoint to poll status
Status	202 (the task was created and scheduled for deployment), 409 (there is a task already for this project and it hasn't finished yet), 400 (a param is missing)

Endpoint ->	/ads-deployment
Purpose	Undeploy an ADS project from the server. Entails removing flows and assets initally supplied
Method	DELETE
Query params	name (the project's name) - mandatory
Status	204 (scheduled for removal), 409 (the project is being deployed currently), 404 (unknown project), 400 (a param is missing)

extracted .gama file example:

Oauth2 scopes:

• GET: https://jans.io/oauth/config/agama.readonly
• Others: https://jans.io/oauth/config/agama.write