HDDS-10142. Add hidden command to set bucket encryption key to fix HDDS-7449

[tanvipenumudy]

What changes were proposed in this pull request?

Due to a known bug: 'HDDS-7449. Avoid overwriting bucket encryption properties when quota/replication config are set on an existing bucket', there can be consumers on a previous version of Ozone who could possibly run into this issue of losing bucket encryption properties when they (re)set quota or bucket replication configurations - which is a critical issue.

Through this patch, we can reset the BEK (bucket encryption key) of buckets affected by this bug through Ozone shell (ozone sh bucket set-encryption-key -k <enckey> <vol>/<buck>).

It does not change any other properties of the bucket or the properties of existing keys in the given bucket.

• The properties of the older keys in the bucket remain as is.
• If any keys are added to the bucket after the bucket loses its encryption (before resetting the BEK), the keys added to the bucket remain unencrypted.
• The newer keys added to the bucket post resetting the BEK are encrypted using the BEK details provided (the fileEncryptionInfo object on the key-level gets generated as expected).

Under normal circumstances, we do not intend for users to (re)set bucket encryption post bucket creation. Therefore, the setter methods introduced, as well as the CLI class have been put behind a @Deprecated annotation.

What is the link to the Apache JIRA

https://issues.apache.org/jira/browse/HDDS-10142

How was this patch tested?

• Added integration tests
• Manually tested
• Green Git CI/CD checks: https://github.com/tanvipenumudy/ozone/actions/runs/7622391450/

[tanvipenumudy]

@adoroszlai, @fapifta could you please take a look? Thanks

[adoroszlai]

Thanks @tanvipenumudy for the patch.

[adoroszlai]

Thanks @tanvipenumudy for updating the patch. I'll let others take a look before merging it.

[errose28]

LGTM thanks @tanvipenumudy

[adoroszlai]

Thanks @tanvipenumudy for the patch, @errose28 for the review.