[Backport fc-26.05-dev] Update FRR to 10.4.1

[platform-pr-manager]

Bot-based backport to fc-26.05-dev, triggered by a label in #2099. Original body:

We've been having issues with unreliable handling of VRFs in FRR, and the advice from upstream has been to upgrade to a more recent version, as there have been VRF-related refactorings and bugfixes which haven't necessarily been backported to older versions. This change bumps the version pin and refreshes the patches.

PL-135068

@flyingcircusio/release-managers

Release process

• Created changelog entry using ./changelog.sh => none, internal change.

PR release workflow (internal)

• PR has internal ticket
• internal issue ID (PL-…) part of branch name
• internal issue ID mentioned in PR description text
• ticket is on Platform agile board
• if ticket is more urgent than within the next few days, directly contact a member of the Platform team

• set urgency and risk labels
• ensure the merge bot has determined a merge date
• ensure all checks are green
• get a review from a colleague

Design notes

• Provide a feature toggle if the change might need to be adjusted/reverted quickly depending on context. Consider whether the default should be on or off. Example: rate limiting.
• All customer-facing features and (NixOS) options need to be discoverable from documentation. Add or update relevant documentation such that hosted and guided customers can understand it as well.

Security implications

• Security requirements defined? (WHERE)
  • Staying up to date with versions of critical software which are actively maintained.
• Security requirements tested? (EVIDENCE)
  • The Hydra tests pass, we're relying on dev and staging to provide a real-world workload test.