Add getProperty.org.bouncycastle.ec.max_f2m_field_size to plugin-security.policy

[cwperks]

Description

Fixes issue related to bouncycastle upgrade where starting up a node with security plugin installed and SAML Authentication enabled resulted in:

Caused by: java.lang.InternalError: cannot create instance of org.bouncycastle.jcajce.provider.keystore.PKCS12$Mappings : java.security.AccessControlException: access denied ("java.security.SecurityPermission" "getProperty.org.bouncycastle.ec.max_f2m_field_sizet")
	at com.amazon.dlic.auth.http.saml.HTTPSamlAuthenticator.<init>(HTTPSamlAuthenticator.java:154) ~[opensearch-security-3.0.0.0-SNAPSHOT.jar:3.0.0.0-SNAPSHOT]
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[?:?]
        ...

Ref: https://github.com/opensearch-project/security-dashboards-plugin/actions/runs/8744995738/job/23999073639?pr=1899

• Category

Maintenance

Check List

• New functionality includes testing
• New functionality has been documented
• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[cwperks]

@reta This permission also needs to be added for SAML authentication. Is there a good way to systematically identify the new permissions that need to be added?

This was caught from e2e tests in the security-dashboards-plugin.

[reta]

Is there a good way to systematically identify the new permissions that need to be added?

Good question, I think we just need more tests since we don't know exactly what permission is needed in what case(s)?

[derek-ho]

Thanks for catching this!