[TextField] Forward name props to the input

[novembrea]

• PR has tests / docs demo, and is linted.
• Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
• Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

Closes #6467.

[novembrea]

I was not sure how strictly you treat don't group multiple topics into one issue concept so I did not include relevant Component API entry update. It might be a good idea to reflect it there, though. I could do this later. For the reference, would that be okay to bundle those thing together?

[mbrookes]

@nvma It's fine to include it with this PR, but not a problem if not, as it will get generate when the docs site is built.

Before you add it though, while @oliviertassinari was reviewing this, I had been looking at other components to see of we had any standard wording for the prop doc string for the case of passing props to sub-components.

I didn't find anything generally (though I didn't look at every component), and this component is all over the place. I think we should standardize on something like:

"XXX attribute of the Input element."

[novembrea]

@mbrookes Thanks for clarification! Surely there's do need to PR for something that could be made automatically.
As to standardizing this usecase in docs I was under impression that @oliviertassinari thought of the name props as a sort of exception to the rule, since you guys don't intend to pass attributes directly to the input.
I myself thought about this and struggled for a couple for minutes looking at your compact descriptions of other props. I thought it would be good to explain why name prop is forwarded directly, but realised that it should be intuitive to anyone working with the framework. It was for me when I was trying to pass the name props, anyways.

[mbrookes]

Surely there's do need to PR for something that could be made automatically.

Actually, that's my mistake. You can create it with npm run build:docs, but this isn't run automatically as part of the distribution build process (npm run build). If you include it with this PR, the docs will be up-to-date for anyone pulling next, if not, it'll be taken care of manually at the next alpha release.

If you could update the prop description following my suggestion, that would be great. If you could also update the other props that are forwarded, even better!

[novembrea]

Yeah, I could do that, no problem. I'll update the PR.