Is your feature request related to a problem? Please describe.

It can be difficult for users to configure the PKCS11 pin to be used by the tedge-p11-server when the customer's applications (including tedge) are running within a container, and don't have access to the tedge-p11-server process or its configuration file.

Describe the solution you'd like

Allow clients to specify the PKCS11 pin to be used for interactions with the tedge-p11-server. Since the tedge-mapper already supports providing the key_uri to tedge-p11-server, allowing the client to also specify the required PIN would all the variable tedge-p11-server configuration to be controlled by the client (all by the PKCS11 module_path, however this is a static value which can be hardcoded when installing tedge-p11-server).

Describe alternatives you've considered

Additional context