Prioritize the bucket configs first during the decommissioning

[Praveenrajmani]

Community Contribution License

All community contributions in this pull request are licensed to the project maintainers
under the terms of the Apache 2 license.
By creating this pull request I represent that I have the right to license the
contributions to the project maintainers under the Apache 2 license.

Description

Currently, the decommissioning will queue the bucket configs and settings in the last. This makes the configs to be decommissioned only after all the data buckets gets decommissioned.

Motivation and Context

To decommission the configs first

How to test this PR?

Not straight forward.
We can check the behavior by writing some DEBUG logs in the decommissioning code.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Optimization (provides speedup with no functional changes)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• Fixes a regression (If yes, please add commit-id or PR # here)
• Unit tests added/updated
• Internal documentation updated
• Create a documentation update request here