SchemaIO should encode config object in the top-level schema

The Java ExpansionService has logic for re-ordering fields based on the client's reported schema and the expanding transforms expected schema.

Currently SchemaIO bypasses this by placing the config object as encoded bytes in a field in the top-level schema. This can cause issues like BEAM-14230.