Added .exclude to Connectable

[azidar]

Added a .exclude mechanism to Connectable, allowing fields to always be ignored by any connectable operator.

This is useful for omitting all Analog types from a bundle, prior to connecting it. I believe we should then make the directioned operators (:=, :#=, :<>= etc.) just error if it encounters an Analog type, but that can be a future PR.

This also jives with #3088 as probe types should also be omitted, as they have their own "connection-like" API called define.

Contributor Checklist

• Did you add Scaladoc to every public function/method?
• Did you add at least one test demonstrating the PR?
• Did you delete any extraneous printlns/debugging code?
• Did you specify the type of improvement?
• Did you add appropriate documentation in docs/src?
• Did you request a desired merge strategy?
• Did you add text to be included in the Release Notes for this change?

Type of Improvement

• Feature (or new API)

Desired Merge Strategy

• Squash: The PR will be squashed and merged (choose this if you have no preference.

Release Notes

Added .exclude mechanism on Connectable to enable never connecting to/from the marked fields using any connectable operator.

Reviewer Checklist (only modified by reviewer)

• Did you add the appropriate labels? (Select the most appropriate one based on the "Type of Improvement")
• Did you mark the proper milestone (Bug fix: 3.5.x or 3.6.x depending on impact, API modification or big change: 5.0.0)?
• Did you review?
• Did you check whether all relevant Contributor checkboxes have been checked?
• Did you do one of the following when ready to merge:
  • Squash: You/ the contributor Enable auto-merge (squash), clean up the commit message, and label with Please Merge.
  • Merge: Ensure that contributor has cleaned up their commit history, then merge with Create a merge commit.

[seldridge]

LGTM

[mwachs5]

the docs make sense to me!

[jackkoenig]

LGTM but 1 request and 1 question.