[Chips] Move MDCChipField text input to a new line if text is too wide

[bryanoltman]

Updates MDCChipField to move the internal text field down to a new line if:

1. The textField is on the same line as chips and becomes too long to fit
2. The textField is on the line below chips but can fit on the line with chips

Fixes #9006

This completes the roll-forward of #9828

Before:

After:

[material-automation]

bazel detected changes to the following targets:

//components/Chips:snapshot_tests
//components/Chips:snapshot_tests_test_bundle
//components/Chips:unit_tests
//components/Chips:unit_tests_IPAD_PRO_12_9_IN_9_3
//components/Chips:unit_tests_IPAD_PRO_12_9_IN_9_3_test_bundle
//components/Chips:unit_tests_IPHONE_7_PLUS_IN_10_3
//components/Chips:unit_tests_IPHONE_7_PLUS_IN_10_3_test_bundle
//components/Chips:unit_tests_environment
//components/Chips:unit_tests_environment_test_bundle

[material-automation]

bazel detected changes to the following targets:

//components/Chips:Chips
//components/Chips:ObjcExamples
//components/Chips:SwiftExamples
//components/Chips:Theming
//components/Chips:privateHeaders
//components/Chips:snapshot_test_lib
//components/Chips:snapshot_tests
//components/Chips:snapshot_tests.swift_runtime_linkopts
//components/Chips:snapshot_tests_test_binary
//components/Chips:snapshot_tests_test_bundle
//components/Chips:unit_test_sources
//components/Chips:unit_test_swift_sources
//components/Chips:unit_tests
//components/Chips:unit_tests_IPAD_PRO_12_9_IN_9_3
//components/Chips:unit_tests_IPAD_PRO_12_9_IN_9_3.swift_runtime_linkopts
//components/Chips:unit_tests_IPAD_PRO_12_9_IN_9_3_test_binary
//components/Chips:unit_tests_IPAD_PRO_12_9_IN_9_3_test_bundle
//components/Chips:unit_tests_IPHONE_7_PLUS_IN_10_3
//components/Chips:unit_tests_IPHONE_7_PLUS_IN_10_3.swift_runtime_linkopts
//components/Chips:unit_tests_IPHONE_7_PLUS_IN_10_3_test_binary
//components/Chips:unit_tests_IPHONE_7_PLUS_IN_10_3_test_bundle
//components/Chips:unit_tests_environment
//components/Chips:unit_tests_environment.swift_runtime_linkopts
//components/Chips:unit_tests_environment_test_binary
//components/Chips:unit_tests_environment_test_bundle
//components/schemes/Shape:ObjcExamples

[jverkoey]

No affected test?

Also: love the clarity of this code. Thank you! 🙏

[jverkoey]

As mentioned in the other thread, I'm somewhat under the UX impression that the chip input text field should always be on a newline to avoid the jumping behavior being coded here, but am not blocking this PR in terms of it being an iterative improvement.

[bryanoltman]

@jverkoey This is kind of tough to test – setting the text programmatically (vs. entering it via keyboard) causes a layout pass, which masks the bug in snapshot tests. Is there a good way to simulate keyboard input? If so, I'll write a couple tests and land those before this PR.

[jverkoey]

Hmm we don't have any tests that I'm aware of that do text input simulation, so that may be a reasonable thing to file as a follow-up issue.