Allow Buddy to exceed the max_connections configuration.

[donhardman]

Proposal:

We should implement the logic to allow Buddy to use its own connections without limitations. This means the max_connections parameter in the configuration should not affect Buddy, because it's the sidecar that should operate without external limitations and is used only to extend the functionality of the daemon.

To achieve this, we should try to detect the connection source. In cases where it originates from Buddy, which can also be determined by checking the User-Agent, we should not apply the maxed out error. Otherwise, the standard logic should still apply.

Checklist:

^{To be completed by the assignee. Check off tasks that have been completed or are not applicable.}

• Task estimated
• Specification created, reviewed and approved
• Implementation completed
• Tests developed
• Documentation updated
• Documentation proofread
• Changelog updated
• OpenAPI YAML updated and issue created to rebuild clients