Consolidate client registration implementation

[WhitWaldo]

Description

To date, we have several standalone clients from the standard Dapr.Client package and these use a common static client builder alongside separate (but similar) static extension registration methods. This PR eliminates duplicate code by introducing a common generic extension method that each of these standalone clients utilize instead of their current separate-but-identical approaches.

This also consolidates how the clients are built to have them work in a consistent way through.

• Dapr.Jobs now reflects the same internal DaprJobsGrpcClient as the other client.
• All clients implement IDisposable to do cleanup on their respective HttpClient instances.
• All client builder implement a local interface facilitating future fluent registration operations globally and on a per-type basis (similar to how Aspire does this).
• This sets the groundwork to remove a dependency going forward on the static builder and rely strictly on DI (which would be necessary with proposed changes to client serialization)

Added unit tests throughout to validate everything.

Issue reference

We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.

Please reference the issue this PR will close: #[issue number]

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

• Code compiles correctly
• Created/updated tests
• Extended the documentation - not necessary, no breaking changes made (all example projects build without error or change)