Secure Area Interface: add supportedAlgorithms functionality

[paulbastian]

The createKey functionality is sending an ecCurve identifier and sign functionality is sending a signature algorithm.
For both, the caller cannot know the possible, supported algorithms.
Especially a wallet core (e.g. implementing OpenID4VCI) needs to negotiate algorithms between the issuer and the secure area.
The proposed solution is therefore to add a supportedAlgorithms functionality to the Secure Area interface.

[davidz25]

I think that makes sense. We should probably also include supportedCurves: List<EcCurve> for good measure.