Allow a developer to test the Canton KMS Driver API integration with the CN QS

This issue is for tracking purposes ...

BNP want to build a Daml 3 application that integrates with their internal HSM / KMS solution. They will use the Canton KMS Driver API for this. This was available in Canton 2 as the [Canton KMS Driver Developer Guide](https://docs.daml.com/canton/usermanual/kms/kms_driver_guide.html). The Daml 3 docs are [here](https://docs.digitalasset.com/operate/3.3/tutorials/kms_driver_guide).

The development of the KMS driver should be done on a plain old JVM running Canton and I would expect integration tests to be done in a similar manner.

So, this would be enabling the installation of the driver binary and associated files onto the Validator node. It should not require application changes. Try to make this a documentation solution using existing QS extension with as few changes as possible.

It is expected that other organizations will want to use KMS as well, with their own KMS driver.

Compare the Canton KMS Driver Developer Guide with the Daml 3 KMS driver guide, then inspect the existing QS extension and Validator node setup. Verify how a driver binary and associated files can be installed on a plain JVM running Canton and how integration tests can exercise the API. Done means the documentation enables this without application changes.

Written by the indexing model from the issue text.