ysql: don't persist table_oid reloption

[jaki]

Jira Link: [DB-385](https://yugabyte.atlassian.net/browse/DB-385)
The table_oid reloption is not something that needs to be persisted to pg_class because it is only used at create time. In transformRelOptions, the oids reloption can be stripped out if ignoreOids is true (@frozenspider pointed this out to me). Similarly, we can always strip out table_oid options (and any others if appropriate).

DefineIndex calls transformRelOptions so that stmt->options holds the old options before transformation and reloptions holds the new options. Therefore, we can still read table_oid from the old options after transformRelOptions, though I think it may be cleaner to stop using it after transformRelOptions.

However, watch out for compatibility with existing clusters that may already have useless table_oid reloptions persisted.

Also, it could be useful to know that the table was created with the table_oid option, but I can't come up with any reasons. If there is a reason, this issue is invalid. cc: @hulien22

[frozenspider]

I think the valid reason to know this as of now if YSQL backup/restore for colocated tables (cc @OlegLoginov), where we actually rely on it.
We plan to change this soon though, decoupling table_oid and an internal colocation_id.

[OlegLoginov]

Related issue: #7378

[tverona1]

This is not relevant for colocation

[frozenspider]

UPD: The only area where this reloption is still used in YSQL upgrade (#10651).

We did remove it from colocation (replaced with colocation_id) and backup/restore (piggyback on PG binary upgrade instead)