fix(web-components): add current-value attribute to TextInput component

[radium-v]

New Behavior

Adds the current-value attribute and currentValue property to the <fluent-text-input> element.

Related Issue(s)

• Fixes [Bug]: fluent-text-input - The second update is not displayed #33137

[fabricteam]

📊 Bundle size report

✅ No changes found

[marchbox]

Could you elaborate a bit on why we need current-value and how that fixes the bug? Just wanted to make sure we have somewhere to reference back to if similar issue occurs again in the future.

[radium-v]

@marchbox for inputs, binding to the value attribute isn't possible since value attribute represents the component's initial/default value, not its current value. Changing the value attribute after a user has interacted with it has no effect on the current value.

Some systems, like Blazor, use attribute bindings to sync states between the client and the server. Providing a current-value attribute that can be tied directly to the value property is a convenience when the alternative would require extra layers of complexity.

(The current-value attribute is something we supported on Foundation controls for this same reason, via the now unused FormAssociated class mixin.)

[github-actions]

📊 Bundle size report

✅ No changes found

[github-actions]

Pull request demo site: URL

[fabricteam]

🕵 fluentui-web-components-v3 No visual regressions between this PR and main