Major Description
While testing async replication handling and failover handling for region replicas, we've found that sometimes the secondary region replicas do not open and update meta quickly enough, and hence meta would not contain any information about the region replica id.
If a reader caches the meta row before all region replicas are open the first time (such as the async wal replication endpoint), then it may miss the region replica and won't know about it until it refreshes it's cache again.
Instead, we should add entries to the meta for all of the region replicas at the time of create table (just like primary regions).