Dev services: MSSQL reactive client does not support JDBC url format

[tsegismont]

Fixes #25233

The "encrypt" property is not needed anyway, it is the default of both the JDBC and reactive clients.

https://docs.microsoft.com/en-us/sql/connect/jdbc/understanding-ssl-support?view=sql-server-ver15#remarks

[tsegismont]

@cescoffier wdyt about backporting?

[gsmet]

I wonder if we should rather generate two different URLs, one for JDBC and one for reactive.
If you do it in the classes like MSSQLDevServicesProcessor, you would have the url parameters map handy so you could filter them far more effectively.

Note that it is a proposal, maybe it's going to be too much maintenance for too little benefits, I don't know.
You could also make it optional i.e. if you push a specific reactive URL, you use it and if not you rely on your dark magic.
But I'm worried the dark magic will be brittle.

[cescoffier]

Same comments as Guillaume, but I think that except about encrypt it looks good.

[tsegismont]

@gsmet I've updated the PR following your suggestions. It looks better indeed.

[cescoffier]

I think it should be backported

[tsegismont]

@cescoffier thank you for reviewing again. I'll wait for @gsmet 's approval and then create a PR for 2.8 branch.

[tsegismont]

@gsmet anything else that needs to be addressed?

[cescoffier]

@tsegismont just add the backport label, no need to create a separate PR (except if we @gsmet asks for it)

[gsmet]

I'll have another look on Monday.