[release/9.0] Fix config source gen binding with SslClientAuthenticationOptions

[github-actions]

Backport of #107579 to release/9.0

/cc @tarekgh

Customer Impact

• Customer reported
• Found internally Configuration Binder source generator generates uncompilable code for SslClientAuthenticationOptions #107003

[Select one or both of the boxes. Describe how this issue impacts customers, citing the expected and actual behaviors and scope of the issue. If customer-reported, provide the issue number.]

When using configuration in the Aspire dashboard, the source generator may produce uncompilable code, leading to compilation errors. This occurs because the source generator wasn't correctly handling certain types (e.g., SslClientAuthenticationOptions) that have properties with unbindable types, yet it still generates code attempting to initialize bindings for them.

Regression

• Yes
• No

[If yes, specify when the regression was introduced. Provide the PR or commit if known.]

Testing

The regression tests have passed, and additional tests were added to cover the previously broken cases.

[How was the fix verified? How was the issue missed previously? What tests were added?]

Risk

Not high as the fix is scoped to the broken case.

[High/Medium/Low. Justify the indication by mentioning how risks were measured and addressed.]

IMPORTANT: If this backport is for a servicing release, please verify that:

• The PR target branch is release/X.0-staging, not release/X.0.

• If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/area-extensions-configuration
See info in area-owners.md if you want to be subscribed.

[tarekgh]

CC @artl93 @ericstj

[tarekgh]

/ba-g no real failure there. Ci just skipped one leg analysis.

[artl93]

Merging per comment above after discussing.