RFC: Remove or separate inline label variant of text field

[DRiFTy17]

The inline or "floating label" variant of the text field (more specifically the shared <forge-field> element) that we adopted from Material is a pattern that we have been discussing moving away from in favor of labels outside (above or to the left of the field). As we look to a new major version, we should consider setting the default label position to our "block start" position, and then we need to determine what to do with the inline variant.

Option #1: Remove completely

We could potentially look to remove the inline/floating label variant altogether, which has long been a source of frustration for both UX designers using the library and library maintainers due to the complexity and challenges that it presents. We would need to consider how this may affect our mobile design as floating labels are more common on mobile platforms with larger touch targets.

Option #2: Separate out to own component

We could also separate the inline variant to its own component where the complexity can be maintained in isolation to avoid side effects with other styles in the text field. This would also allow for more explicitly opting in to either variant.

Option #3: Do nothing

We could also choose to keep these variants together, and go with inline as our desired default. I don't believe this will be a popular option, but I wanted to make it known that it is on the table for discussion.