cert_distribute.sh script should allow customized new client cert file names

In the current implementations, the cert_distribute.sh shell script at levels 8.1.21 and 8.1.22 is using random file names for the newly created client cert (crt) file. 
For customer environments with multiple, maybe hundreds of Storage Protect servers, a random file name will not allow customer to easily identify the Storage Protect server the new certificate file belongs to. It may become even more complicated in case the same Storage Protect client will connect to multiple Storage Protect servers; this would require to run cert_distribute.sh multiple times, creating random new client cert files multiple times. When using random file names for the newly created client crt file it will be not possible to identify the corresponding Storage Protect server just from looking to the random client crt file names.

The cert_distribute.sh shell script should allow customers to customize the file name of the newly created client crt file so that the file name will match customer needs.
This could be done, for example, by adding a new option to the cert_distribute.ini file, allowing customer to preset the name of the new client crt file. 
The same name should be use as label for the new certificate when adding it to the clients certificate database.

Another option would be to use the name of the (input) *.arm file the cert_distribute.sh script uses to read the newly generated certificate, maybe with an appended random string to ensure the new crt file name will be unique.
Example: 
cert_distribute.ini - newcertfile = SP_SRV_001_2024-04-03.arm
may result into new client crt file name
   SP_SRV_001_2024-04-03.crt 
or 
  SP_SRV_001_2024-04-03_randomstring.crt