iptables: add back missing kernel modules for iptables

[dallasd1]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

Add back missing kernel modules for iptables introduced by change that enabled nftables

Change Log

• Add new config to load iptables kernel modules to the iptables package

Does this affect the toolchain?

NO

Associated issues

• #xxxx

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-YYYY-XXXX

Test Methodology

• buddy build: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=714629&view=results
• image build: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=714643&view=results
• e2e tests: https://dev.azure.com/msazure/CloudNativeCompute/_build/results?buildId=112875184&view=results
• e2e tests with kernel upgrade: https://dev.azure.com/msazure/CloudNativeCompute/_build/results?buildId=112875143&view=results

[mfrw]

should we add these modules as well:

ipt_ah 
ipt_ECN 
ipt_REJECT 
ipt_rpfilter 
ipt_SYNPROXY

Rationale: When i did a repro locally, I could see these modules also

[dallasd1]

Were these enabled by default with the previous iptables package or only after the repro? If they weren't loaded before the repro, I don't think we'd want to add them to the conf file