[API] Firewall: support IP ranges and accept/drop

[Wekkser]

This pull request introduces enhancements to the firewall package, including the addition of support for IP ranges and new filter actions.

Improvements to IP value handling:

• Added support for IP ranges by introducing a new IPValueTypeRange constant and updating the GetIPValueType function to recognize IP ranges.

• Updated the applyMatchIP function to handle IP ranges and added the applyMatchIPRange function for applying IP range matches.

Enhancements to firewall actions:

• Added new filter actions ActionAccept and ActionDrop to the FilterAction enum and updated the FilterRule struct to include these actions.

• Implemented the applyAcceptAction and applyDropAction functions to apply the new accept and drop actions in the firewall rules.

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration.

• Test A
• Test B

[adamjensenbot]

Hi @Wekkser. Thanks for your PR!

I am @adamjensenbot.
You can interact with me issuing a slash command in the first line of a comment.
Currently, I understand the following commands:

• /rebase: Rebase this PR onto the master branch (You can add the option test=true to launch the tests
  when the rebase operation is completed)
• /merge: Merge this PR into the master branch
• /build Build Liqo components
• /test Launch the E2E and Unit tests
• /hold, /unhold Add/remove the hold label to prevent merging with /merge

Make sure this PR appears in the liqo changelog, adding one of the following labels:

• feat: 🚀 New Feature
• fix: 🐛 Bug Fix
• refactor: 🧹 Code Refactoring
• docs: 📝 Documentation
• style: 💄 Code Style
• perf: 🐎 Performance Improvement
• test: ✅ Tests
• chore: 🚚 Dependencies Management
• build: 📦 Builds Management
• ci: 👷 CI/CD
• revert: ⏪ Reverts Previous Changes