Replace TBD XML doc placeholders in UDP IO files

[MattKotsenas]

Partial fix for #3435, contributes to #647.

Changes

Document all TBD XML doc blocks in the UDP-related IO files:
UdpConnection, UdpListener, UdpSender, UdpConnectedManager, UdpManager, and UdpSettings.

Doc-only change - no behavioral modifications.

Checklist

• This change follows the Akka.NET API Compatibility Guidelines.
• I have reviewed my own pull request.
• Changes in public API reviewed, if any.

[Aaronontheweb]

Looks good minus a few guidelines about not XML-DOCing overridden base class methods

[Aaronontheweb]

Probably don't need any XML-DOCs at all for this - the natural inheritdoc from the base class should be sufficient.

[Aaronontheweb]

Same as my comment on PostStop

[MattKotsenas]

My bad, will fix!

[Aaronontheweb]

My bad, will fix!

All good, it's tricky - if you're using LLMs to do this you'll want to add something to the prompt like this:

Replace all TBD XML-DOC comments with a meaningful, helpful comment that explains what the interface / class / method does without merely repeating what can be obviously inferred from the variable names. If this class / interface / member inherits or implements a base type that already has a substantive XML-DOC declared, simply delete the existing XML-DOC so the base types' one gets inherited automatically.

[MattKotsenas]

Do you want a delete, or do you want an explicit ?

[Aaronontheweb]

I'd delete the XML-DOC comment - correct me if I'm wrong, but the child classes / implementations will inherit the base types comments in intellisense, right?

[MattKotsenas]

I just double checked and yes, if you have nothing, Intellisense does automatically pick up the base type's xmldoc.

Convention on my team is always to use <inheritdoc/> so it's clear that's the intention versus looking like "you forgot", but I'm OK with omission as well. Making changes and doing a pass through PRs now.

[Aaronontheweb]

Convention on my team is always to use so it's clear that's the intention versus looking like "you forgot", but I'm OK with omission as well.

that's a good point, maybe it's better that we do that then as a signal to other contributors that "this is covered already"

[MattKotsenas]

@Aaronontheweb, updated (with explicit inheritdoc). Ready for another review. Double checking the other open PRs under my name now.

[Aaronontheweb]

LGTM