Describe the bug

Although AtOnboardingPreference takes AtSigningAlgo and AtHashingAlgo as optional inputs. There is no way as of now to pass that same data to AtAuth. This causes AtAuth to perform Auth using the default values for Signing and Hashing algo.

Steps to reproduce

1. Create an instance of AtOnboardingCli, where the AtOnboardingPreference mentions AtSigningAlgo to be 'ecc_secp256r1'
2. In the above step, ensure to pass ecc type Public and Private keys for pkam/apkam authentication
3. Set the AtSignLogger root level to FINER
4. Call AtOnboardingService.authenticate()
5. PKAM authentication fails
6. On finding the command that is sent to perform pkam authentication, the command would still mention that AtSigningAlgo is RSA.

Expected behavior

The pkam authentication command should specify whichever SigningAlgo mentioned in the AtOnboardingPreferences

Additional context

One possible solution could be adding new params for AtSigningAlgo and AtHashingAlgo in AtOnboardingRequest, which is used to pass params from AtOnboardingCli to AtAuth.