[release/8.0] [Blazor] Pass the member info directly

[github-actions]

Backport of #53874 to release/8.0

/cc @javiercn

[Blazor] Pass the member info directly

Avoids using Expression.PropertyOrField as it can throw an exception when a type contains multiple members of the same type with different casing.

Description

When users define multiple properties or fields that only differ in casing, Blazor throws an exception when the user uses one of our inputs components as part of a form.

For example:

<EditForm ...>
  <InputText @bind-Value="field" />
</EditForm>

@code
{
  public int field;
  public int Field;
}

Fixes #52755, #53891

Customer Impact

• We've received feedback from 3 customers.
• There is no workaround that doesn't require customers to change their code (not possible if code is in a library).
• Regresses previous scenarios that worked in 7.0 (even if the scenarios can be considered an edge case).

Regression?

• Yes
• No

7.0

Risk

• High
• Medium
• Low

We've added automated tests to cover this scenario and ensure it works. We've also replaced the problematic code with a simpler version where the problematic function is not invoked.

Verification

• Manual (required)
• Automated

Packaging changes reviewed?

• Yes
• No
• N/A

---

When servicing release/2.1

• Make necessary changes in eng/PatchConfig.props