Use Azure Edge Server rather than MS SQL on Mac M1

[holly-cummins]

Partial resolution of #25428. See also discussion in #25648.

To test,

mvn clean 
mvn -Dquickly 
TESTCONTAINERS_RYUK_DISABLED="true" ./mvnw -Dquickly -DskipTests=false -Dstart-containers -f  extensions/reactive-mssql-client/deployment/pom.xml
TESTCONTAINERS_RYUK_DISABLED="true" ./mvnw -Dquickly -DskipTests=false -Dstart-containers -Dtest-containers -f extensions/jdbc/jdbc-mssql
TESTCONTAINERS_RYUK_DISABLED="true" ./mvnw -Dquickly -DskipTests=false -Dstart-containers -Dtest-containers -f integration-tests/jpa-mssql
TESTCONTAINERS_RYUK_DISABLED="true" ./mvnw -Dquickly -DskipTests=false -Dstart-containers -Dtest-containers -f integration-tests/reactive-mssql-client           

The clean and rebuild is needed to avoid issues relating to licence-non-acceptance of the changed image name.

What's changed?

The MS SQL image segfaults on ARM. The best option seemed to be the widely recommended workaround of using Azure Edge Server. The two products are not functionally interchangeable, but there is enough similarity to make it worth running this way.

Note: this change will also affect dev services if built locally, but not in the official releases, unless they are built on M1. I think that’s kind of weird but kind of ok, but I’m open to objections if people think that's too inconsistent.

[quarkus-bot]

Thanks for your pull request!

The title of your pull request does not follow our editorial rules. Could you have a look?

• title should not end up with dot

This message is automatically generated by a bot.

[Sanne]

Looks safe to me! I can't test it and needs a conflict resolved, so I'll approve already so you can merge it right away when you have a moment to fix it.

[gsmet]

I fixed the conflicts, let's merge this.

[holly-cummins]

Thanks @gsmet, you beat me to it!