change: allow different protocols on the same port (manager#1566)

[iwilltry42]

Ref https://github.com/acorn-io/manager/issues/1566

With this, it's OK to expose the same port/targetPort combination as long as they're using different protocols (which are non-blocking).

Checklist

• The title of this PR would make a good line in Acorn's Release Note's Changelog
• The title of this PR ends with a link to the main issue being address in parentheses, like: This is a title (#1216). Here's an example
• All relevant issues are referenced in the PR description. NOTE: don't use GitHub keywords that auto-close issues
• Commits follow contributing guidance
• Automated tests added to cover the changes. If tests couldn't be added, an explanation is provided in the Verification and Testing section
• Changes to user-facing functionality, API, CLI, and upgrade impacts are clearly called out in PR description
• PR has at least two approvals before merging (or a reasonable exception, like it's just a docs change)

[iwilltry42]

I feel like this should throw an error/warning way earlier in the process instead of just dropping some ports without further notice. Any opinions on this?

[keyallis]

Generally looks good, requested a logic change and potentially another test case

[tylerslaton]

Approving with the assumption that @keyallis's feedback is addressed. That's the only thing blocking in my mind here.

[iwilltry42]

Fixed the logic to match what we discussed before - added related comments.
I also had to update quite a bunch of other files to make the revive linter happy 😬