75 enhance typer application with readiness check bypass and advanced firewall inventory management

[cdot65]

This pull request introduces a series of updates and bug fixes aimed at improving the functionality and user experience of our application. The changes are detailed below based on the commit history:

1. Update settings subcommand menu to support bypassing all readiness checks:

   • Enhanced the "settings" subcommand menu to include an option that allows users to bypass all readiness checks, catering to advanced users who require more control and speed in their workflows.

2. Swap active and passive roles for woodlands-fw1 and woodlands-fw2:

   • Modified the roles of woodlands-fw1 and woodlands-fw2 to ensure optimal load balancing and failover capabilities, enhancing system reliability and performance.

3. Refactor logging statements in determine_upgrade function:

   • Improved the clarity and usefulness of logging statements within the determine_upgrade function, making it easier to diagnose issues and understand the upgrade process flow.

4. Add pan-os-upgrade.code-workspace to .gitignore:

   • Ensured that workspace settings specific to Visual Studio Code do not clutter the repository, keeping the project clean and focused.

5. Update version to 1.1.6 in pyproject.toml:

   • Bumped the project version to 1.1.6 in pyproject.toml, preparing for the new release with all the included enhancements and fixes.

6. Update default value for ARP Table snapshot:

   • Adjusted the default behavior regarding ARP Table snapshots to align with the latest operational best practices, improving the application's default configuration state.

7. Add release notes for versions 1.1.6:

   • Compiled and documented the release notes for versions 1.1.6, ensuring that users are well-informed about the changes, improvements, and fixes introduced in these releases.

8. Update pan-os-upgrade version to 1.1.6:

   • Finalized the version update process by setting the application version to 1.1.6 across all relevant files and documentation, marking the culmination of this development cycle.

These changes collectively aim to enhance the application's functionality, user experience, and reliability. We encourage a thorough review and welcome any feedback or suggestions to further refine these updates.

Testing:

• Each update has been thoroughly tested to ensure compatibility and performance. Test cases covered various scenarios, including edge cases, to ensure the reliability of these changes.

Documentation:

• Relevant documentation has been updated to reflect these changes, including updated usage instructions, configuration options, and release notes.

We believe these updates will significantly contribute to the project's value and look forward to the community's feedback and contributions.