Update CITE tests to the production images where possible

[aaime]

This PR updates a number of CITE tests and switches them to the production docker image of the teamengine, starting them up with the REST API. Exceptions:

• WCS 1.0 has no way to be started with REST, I would not hold my breath waiting for it and the process is not immediate, here is a WCS 1.1 example for reference (and they did not have to split the CTL files into per-request sub-files). I also could not get to pass the test suite due to some oddball issue invoking a XSTL function... however, running the WCS 1.0 CITE tests from the web interface works (so it could be used for certification, even if we cannot keep tabs on it).
• WFS 1.1 fail to work when invoked through the REST API, apparently due to a Teamengine packaging issue. When that is fixed, we can switch this one to latest as well.

In order to get things passing with all the suites, I had to centralized the version negotiation, and pull some hacks to identify the version of ServiceException the WCS test demand (they don't provide the version number, and assume one still responds with the ServiceException from the WCS being tested).

Checklist

• I have read the contribution guidelines.
• I have sent a Contribution Licence Agreement (not required for small changes, e.g., fixing typos in documentation).
• First PR targets the main branch (backports managed later; ignore for branch specific issues).
• All the build checks are green (see automated QA checks).

For core and extension modules:

• New unit tests have been added covering the changes.
• Documentation has been updated (if change is visible to end users).
• The REST API docs have been updated (when changing configuration objects or the REST controllers).
• There is an issue in the GeoServer Jira (except for changes that do not affect administrators or end users in any way).
• Commit message(s) must be in the form [GEOS-XYZWV] Title of the Jira ticket.
• Bug fixes and small new features are presented as a single commit.
• Each commit has a single objective (if there are multiple commits, each has a separate JIRA ticket describing its goal).

[groldan]

Amazing