Support AWS credentials file creation with profiles

[poikilotherm]

In the 4.20 release, Dataverse introduced support for multiple storage locations. Using S3 technology there is an assumption that ~/.aws/credentials not only contains a [default] entry, but also supports the usage of [profile]s.

We need to respect that in init_1_conf_glassfish.sh and init_2_conf_payara.sh by adding support to create the file including profiles from the S3 secret.

The "storage driver id" has been changed, too. Now this references to the id of a storage location used as default for dataverses not having chosen another storage location. So creating the credential file should not anymore rely on what driver id is used, but create them anyway if present.

The idea is to reuse the existing mechanism to be backward compatible. (The secret might be used for other purposes like feeding the key to a Minio deployment!) To add profiles, one has to prefix the access-key and secret-key with the profiles name, like foo-access-key.