Accept "EdDSA" as the JCA key algorithm name when generating Ed25519 keys.

Conscrypt added support for Ed25519 signatures in
https://github.com/google/conscrypt/commit/5473d34964ce77ab2594ae0cc0ecf74931f28cc3.
This involved introducing a "OpenSslEdDsaPublicKey" class that returns
"EdDSA" as the algorithm name and is registered in the
"OpenSSLProvider".

When the "AndroidKeyStoreProvider" generates a key pair, the public key
operations are delegated to the "OpenSSLProvider". It uses the
"OpenSSLX509Certificate" class to extract the key algorithm name from
the public key's X.509 certificate. If the OID in the certificate can't
be mapped to an algorithm name, the OID itself is returned in a string
as the algorithm name.

The introduction of the "OpenSslEdDsaPublicKey" class meant that the
"OpenSSLProvider" was able to produce a more meaningful key algorithm
name, but the "AndroidKeyStoreProvider" didn't recognize it since the
OID was hard-coded in the algorithm validation logic to reflect the
fallback logic in the "OpenSSLX509Certificate" class. This caused the
Android Keystore CTS tests related to Ed25519 to fail due to the
unrecognized algorithm name and the merge had to be reverted. See
ag/34292636.

This fix accepts both the OID and "EdDSA" as algorithm names. Once the
upstream Conscrypt changes get merged into Android and are stable for
a while, we can stop accepting the OID.

Bug: 430870763
Flag: EXEMPT BUGFIX
Test: atest CtsKeystoreTestCases:android.keystore.cts.Curve25519Test
      (with the OpenSSLProvider changes manually patched)
Test: atest CtsKeystoreTestCases:android.keystore.cts.KeyAttestationTest
      (with the OpenSSLProvider changes manually patched)
Change-Id: I4fc42e46cfbeaaca5691bdaf03af98417fe8192d