Add a new write_only_allow_delete indexing block

[Gaurav614]

Description

Added a new write_only_allow_delete block for indices.
This was proposed here: #12362

[Describe what this change achieves]
This will allow user to manually add block that has similar permissions as read_only_allow_delete block, since read_only_allow_delete is used only for internal purposes

 curl -X PUT "localhost:9200/test-2/_block/read_only_allow_delete?pretty"

{
  "error" : {
    "root_cause" : [
      {
        "type" : "action_request_validation_exception",
        "reason" : "Validation Failed: 1: read_only_allow_delete block is for internal use only;"
      }
    ],
    "type" : "action_request_validation_exception",
    "reason" : "Validation Failed: 1: read_only_allow_delete block is for internal use only;"
  },
  "status" : 400
}

Related Issues

Resolves : #12362

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
• Commits are signed per the DCO using --signoff
• Commit changes are listed out in CHANGELOG.md file (See: Changelog)
• Public documentation issue/PR created

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.

[github-actions]

Compatibility status:

Checks if related components are compatible with change 987dfa9

Incompatible components

Skipped components

Compatible components

Compatible components: [https://github.com/opensearch-project/asynchronous-search.git, https://github.com/opensearch-project/anomaly-detection.git, https://github.com/opensearch-project/performance-analyzer-rca.git, https://github.com/opensearch-project/cross-cluster-replication.git, https://github.com/opensearch-project/reporting.git, https://github.com/opensearch-project/job-scheduler.git, https://github.com/opensearch-project/security.git, https://github.com/opensearch-project/geospatial.git, https://github.com/opensearch-project/common-utils.git, https://github.com/opensearch-project/k-nn.git, https://github.com/opensearch-project/alerting.git, https://github.com/opensearch-project/custom-codecs.git, https://github.com/opensearch-project/neural-search.git, https://github.com/opensearch-project/security-analytics.git, https://github.com/opensearch-project/flow-framework.git, https://github.com/opensearch-project/performance-analyzer.git, https://github.com/opensearch-project/index-management.git, https://github.com/opensearch-project/ml-commons.git, https://github.com/opensearch-project/notifications.git, https://github.com/opensearch-project/opensearch-oci-object-storage.git, https://github.com/opensearch-project/observability.git, https://github.com/opensearch-project/sql.git]

[github-actions]

❌ Gradle check result for 987dfa9: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[andrross]

The name of our blocks are currently inconsistent (e.g. APIBlock.READ blocks reads as one might expect, yet APIBlock.READ_ONLY blocks writes). However, making something named WRITE_ONLY_ALLOW_DELETE be functionally identical to something named READ_ONLY_ALLOW_DELETE doesn't seem to be helping the situation. Given the inconsistency already present, I don't have an obvious alternative suggestion, but can we try to work through a better name if we go forward with this approach?

[opensearch-trigger-bot]

This PR is stalled because it has been open for 30 days with no activity.

[shwetathareja]

There is no plan to take this forward. Closing it for now.