[g31pranjal]

RecordMetaData.getPlannerType takes record type names and resolves them with getRecordType, which only knows stored record types. So the planner cannot describe a synthetic record type. In particular, IndexExpansionInfo cannot build the base type of an index defined on one.

This adds getPlannerTypeForRecordType(RecordType) and getPlannerTypeForRecordTypes(Collection<RecordType>), which describe the record types they are given rather than looking them up by name. The name-taking overloads now resolve their names and delegate to them, so their behaviour is unchanged. IndexExpansionInfo passes the indexed record types it already holds.

Nothing changes observably yet: indexes on synthetic record types are not offered to the planner. This is groundwork for planning queries against indexes on joined synthetic record types (#4817).

RecordMetaDataPlannerTypeTest covers three cases:

• the new overload describes a joined record type, which the name-taking overload rejects;
• for stored types, the new overloads agree with the name-taking ones, including the version pseudo-field when versions are stored;
• several types are described by the union of their fields, and a single type exactly as on its own.