Support logical types when translating the portable row coder representation

[damccorm]

Originally SchemaCoder and RowCoder relied on including serialized java classes and functions to support logical types, but the portable schema representation only includes a URN for a logical type. We will need to be able to re-construct logical types given just a URN, presumably by creating some sort of logical type registry indexed by URN.

Imported from Jira BEAM-7855. Original Jira may contain additional context.
Reported by: bhulette.

[Abacn]

From the TODO mark in source:

beam/sdks/java/core/src/main/java/org/apache/beam/sdk/schemas/SchemaTranslation.java

Line 183 in 3ede5b7

.setUrn(URN_BEAM_LOGICAL_JAVASDK);

Any known but yet standardized logical types (those in STANDARD_LOGICAL_TYPES) will assign the same urn "beam:logical_type:javasdk:v1". These include all jdbc logical types and also many defined in org.apache.beam.sdk.schemas.logicaltypes package. While user can register this URN and implement with there own class in a cross-language pipeline, (e.g. https://stackoverflow.com/questions/68758361/error-beamlogical-typejavasdkv1-while-using-apache-beam-io-jdbc-readfromjdbc), they can do at most one logical type because they share the same URN. Would be preferrable to encode the identifier in URN as well, for example, in the example stackoverflow case, The involved logical type from Java side is org.apache.beam.sdk.io.jdbc.LogicalTypes.VariableLengthString with identifier 'VARCHAR', It would then have URN "beam:logical_type:javasdk_varchar::v1" or "beam:logical_type:javasdk_variablelengthstring::v1" (or "beam:logical_type:javasdk:varchar::v1" or "beam:logical_type:javasdk:variablelengthstring::v1")