Changes in workflow manager modules

[madhansansel]

Description

    - Added sample playbook for Device Configs Backup Module
    - Changes in dnac.py file
    - Bug fixes in accesspoint_workflow_manager module
    - Enhancements in device_configs_backup_workflow_manager module to support unzipped backup file after download
    - Changes in inventory_workflow_manager module
    - Changes in ise_radius_integration_workflow_manager
    - Changes in network_compliance_workflow_manager
    - Changes in network_settings_workflow_manager
    - Bug fixes in sda_fabric_devices_workflow_manager
    - Bug fixes in sda_fabric_transits_workflow_manager
    - Enhancements in sda_host_port_onboarding_workflow_manager module
    - Changes in swim_workflow_manager module
    - Enhancements in device_credential_workflow_manager module
    - Bug fixes in lan_automation_workflow_manager module
    - Enhancements in provision_workflow_manager module
    - Bug fixes in pnp_workflow_manager module
    - Bug fixes in template_workflow_manager module
    - sda_fabric_devices_workflow_manager - attribute 'delete_fabric_device' was removed
    - sda_host_port_onboarding_workflow_manager - attributes 'port_channels', 'fabric_site_name_hierarchy', 'port_assignments', 'wireless_ssids' were added
    - sda_host_port_onboarding_workflow_manager - attributes 'port_channel_details', 'port_assignment_details' were removed
    - device_configs_backup_workflow_manager - attribute 'unzip_backup' was added
    - network_settings_workflow_manager - attribute 'force_delete' was added

Type of Change

• [ YES] Bug fix
• [ YES] New feature
• Breaking change
• Documentation update

Checklist

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

Ansible Best Practices

• [YES] Tasks are idempotent (can be run multiple times without changing state)
• [YES] Variables and secrets are handled securely (e.g., using ansible-vault or environment variables)
• [YES] Playbooks are modular and reusable
• [YES] 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