[FEATURE]Ability to provide customized security configurations to the cluster

[gaiksaya]

Is your feature request related to a problem?

The current opensearch-cluster-cdk configuration in terms of security is either default security config or no security at all.
It would be helpful to be able to provide custom security configuration to the cluster. For example, only specific role mapping, allow anonymous read, etc

What solution would you like?

Ability to provide customized security configurations to the cluster

What alternatives have you considered?

Manually logging into the cluster, changing config followed by cluster restart

Do you have any additional context?

Add any other context or screenshots about the feature request here.

[gaiksaya]

Thinking of extending the scope of this issue to allow overwriting any config file with the custom config file provided by the user. As of 2.11.0 I am seeing below file in config folders and sub-folders:

opensearch]# tree config/
config/
├── discovery-ec2
│   └── log4j2.properties
├── jvm.options
├── jvm.options.d
├── log4j2.properties
├── opensearch-notifications
│   └── notifications.yml
├── opensearch-notifications-core
│   └── notifications-core.yml
├── opensearch-observability
│   └── observability.yml
├── opensearch-performance-analyzer
│   ├── agent-stats-metadata
│   ├── log4j2.xml
│   ├── opensearch_security.policy
│   ├── performance-analyzer.properties
│   ├── plugin-stats-metadata
│   ├── rca.conf
│   ├── rca_cluster_manager.conf
│   ├── rca_idle_cluster_manager.conf
│   └── supervisord.conf
├── opensearch-reports-scheduler
│   └── reports-scheduler.yml
├── opensearch-security
│   ├── action_groups.yml
│   ├── allowlist.yml
│   ├── audit.yml
│   ├── config.yml
│   ├── internal_users.yml
│   ├── nodes_dn.yml
│   ├── opensearch.yml.example
│   ├── roles.yml
│   ├── roles_mapping.yml
│   ├── tenants.yml
│   └── whitelist.yml
├── opensearch.keystore
├── opensearch.yml
└── repository-s3
    └── log4j2.properties

If a user provides for-example a custom config file for /local/path/to/customized-reports-scheduler.yml, and path to the file to be overwritten (in this case /config/opensearch-reports-scheduler/reports-scheduler.yml), the cdk should take care of it.