This PR addresses the issue in #446

In here, I,

• Added a new --no-default-rules flag to control default firewall rule creation.
• Marked --create-rules as deprecated but kept for backward compatibility.
• Added a deprecation warning for --create-rules usage.
• Error out when both the flags are used simultaneously.
• Updated the documentation to reflect the changes.

Why deprecate --create-rules flag ?

If we see the documentation, it seems --create-rules was introduced to give users a way to create firewalls without any default firewall rules set.

But, now that we have --no-default-rules flag, deprecating (not removing) --create-rules I feel is the obvious next step here.

Note: when a flag is deprecated, It continues to function but does not show up in help or usage messages.

Result:

1. Firewall correctly created with default rules without --create-rules flag

2.When we use --create-rules flag, a warning message flashes, but default rule still gets created as before.

3. Backward compatibility not getting affected:

4. Firewall correctly getting created with --no-default-rules

5. No firewall rules applied with --no-default-rules flag

6. Error out when both flags are used:

7. Updated Documentation