Ordered the device_config details before removing the devices from the fabric

[MUTHU-RAKESH-27]

Description

Ordered the device_config details before removing the devices from the fabric
Because the first node that should be added to the fabric is a CONTROL_PLANE_NODE and the last should be deleted from the fabric is also the CONTROL_PLANE_NODE.
If user passes series of devices that to be removed from the fabric, we will order it in such a way that the CONTROL_PLANE_NODE should be removed at last from the fabric.

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• All the sanity checks have been completed and the sanity test cases have been executed

Ansible Best Practices

• Tasks are idempotent (can be run multiple times without changing state)
• Variables and secrets are handled securely (e.g., using ansible-vault or environment variables)
• Playbooks are modular and reusable
• Handlers are used for actions that need to run on change

Documentation

• All options and parameters are documented clearly.
• Examples are provided and tested.
• Notes and limitations are clearly stated.

Screenshots (if applicable)

Notes to Reviewers