Creation of service-keys

[joergdw]

This contains the "app-autoscaler"-changes for cloudfoundry/app-autoscaler-release#3652.

Current top-commit-id of that branch: "9ca68503e2f08bd8123df39b5722decb0fcde1bb"

This PR comes with the following changes:

• Service-key-support
  • Introduce the necessary handling into the Bind-function of the broker.
  • Unit-tests
  • Divide the schema into three logical units for three different scenarios, where the "meta.schema.json" brings all of them together:
    • Creation of a service-key using the default-policy while enforcing the usage of the field schema-version (only allowed value: "0.9").
    • Creation of a service-key with explicitly set policy while enforcing the usage of the field schema-version.
    • All the other use-cases that have been supported until now allowing to skip the schema-version. This is for backwards-compatibility.
• Multi-schema support for binding-requests:
  • Separate logic between request-handling and request-parsing. Introduce the interface BindRequestParser for request-parsers. This is an architectural improvement to simplify maintenance even for a growing variance and seconds the seperation of the internal representation of scaling-policies from their json-representation.
  • Adapt tests to the slighly changed error-messages. This is necessary to support the old schema as well. For acceptance-tests these changes are minimal.
• Makefiles:
  • Fix usage of shell-styles
  • (Re-)Generate fakes and gorouterproxy only if relevant input-files have changed.
  • Fix dependencies (e.g. for autoscaler.test) and recipes.
  • Use programs provided by devbox instead of go run ….
  • Fix target clean.
• Efficiency-improvement: Avoid parsing of the default credential-type for the communication with the metricsforwarder on each request.

[joergdw]

All tests are green at the moment.

[joergdw]

The tests just got green for this revision. We had several flakiness-issues.

[sonarqubecloud]

Quality Gate passed

Issues
16 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
1.0% Duplication on New Code

See analysis details on SonarQube Cloud