Fix: Agent Should Not Hard Fail on Config Values Above Max

[vishal-chdhry]

Signed-off-by: Vishal Choudhary contactvishaltech@gmail.com

Please ensure your pull request adheres to the following guidelines:

• For first time contributors, read Submitting a pull request
• All code is covered by unit and/or runtime tests where feasible.
• All commits contain a well written commit description including a title,
  description and a Fixes: #XXX line if the commit addresses a particular
  GitHub issue.
• If your commit description contains a Fixes: <commit-id> tag, then
  please add the commit author[s] as reviewer[s] to this issue.
• All commits are signed off. See the section Developer’s Certificate of Origin
• Provide a title or release-note blurb suitable for the release notes.
• Thanks for contributing!

When the amount of policy map entries exceeds PolicyMap max entries, instead of a hard exit with code 1, it throws a warning and enforces the hard maximum value.

Fixes: #22070

Automatically adjust `bpf-policy-map-max` if the maximum value is exceeded

[gandro]

Looks good to me. cc @bmcustodio for visibility (iirc you had some thoughts on this as well)

[gandro]

Could you also add some more descriptive release note (either by changing the PR title or by adding a release notes section to your PR description)? For example:

Automatically adjust `bpf-policy-map-max` if the maximum value is exceeded

[tklauser]

The change itself LGTM. Should we change the behavior for other map size values as well?