useTextField et al. create empty value attribute

[brandonpittman]

🐛 Bug Report

In the same vein as #3554, the useTextField hook passes along undefined as the value for value when a value isn't supplied. This causes trouble when submitting forms as GET requests (especially) because it creates searchParam soup in the URL.

🤔 Expected Behavior

1. If no value is passed to an input, no value attribute should exist in the DOM.
2. An empty input shouldn't change the searchParams when submitting a GET request in a form

😯 Current Behavior

1. All inputs created using useTextField have value attributes in the DOM, even when they aren't passed one.
2. Empty inputs add searchParams to the URL like ?emptyInputName=

💁 Possible Solution

Fix is using the same method as checkboxes were recently fixed.

#3554

🔦 Context

I'm trying to create a search filter and the all inputs are submitting empty strings—creating entries for each in the searchParams.

💻 Code Sample

https://codesandbox.io/s/naughty-fast-jg5wp3?file=/src/App.js

If you remove the inputProps from the input, the unnecessary value attribute goes away.

🌍 Your Environment

Software	Version(s)
react-aria.	3.20
Browser	Chrome 106
Operating System	macOS 12.6

🧢 Your Company/Team

Splink Inc.