Fix falsy literal values being mishandled in AccessRules port/network/SGT methods

[Copilot]

Truthiness checks on literal parameters caused valid falsy values (e.g., port 0 as int) to fall through to the object-name lookup path instead of being treated as literals.

Changes

• All five literal-accepting methods (source_port, destination_port, source_network, destination_network, source_sgt): replaced if literal / if literal and name != "" with if literal is not None / if literal is not None and name != "" — 12 occurrences total.

Example

# Before: port 0 (falsy int) silently fell through to object-name lookup
rule.source_port("add", literal=0, protocol="TCP")  # BUG: treated as no literal

# After: correctly routes to literal handling path
rule.source_port("add", literal=0, protocol="TCP")  # OK

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.