UI - Autofill breaks during table creation if table name != schema name.

Hello,

When creating a table whose name does not match exactly the name of an existing schema the UI will not provide auto-complete functionality regarding which fields we can use. The workaround is to copy/paste a json definition a table that matches the schema and then manually edit the json as necessary.

Steps to reproduce.
1.) Create a schema with some fields with name XXX.
2.) Try to create table with name XXX-"extra" (name will not match).
3.) No schema field information will be available to assist the table creation process.

A similar action happens if you try to copy paste a table definition into the json textbox, if you change the table name, then `segmentsConfig.timestamp` will automatically be reset and you have to re-type it even though it may be correct.

Thank you.

Start in the table-creation UI, reproduce the schema and table name mismatch, and inspect the autocomplete behavior and JSON textbox handling. Done means fields remain available when the table name differs from the schema name and changing a pasted table name does not reset a valid segmentsConfig.timestamp value.

Written by the indexing model from the issue text.