Fix blind replace of d. in TypedLocator causing issues when schema name ends with d

[mysticmind]

• Fix blind replace of d.in TypedLocator causing issues when schema name ends with d
• Fixes Schema name ending with d results in issues with generated index definitions #3778

[mysticmind]

The CI failure DocumentDbTests.Bugs.Bug_2169_concurrency_error.there_should_be_no_error [FAIL] is unrelated to this PR.

[aarearnold]

If the index contains a reference to the additional column (for example, a column used as a foreign key), the SQL becomes invalid because d. no longer gets replaced.

output prior this PR:
CREATE UNIQUE INDEX mt_doc_user_accounts_uidx_provider_nameuser_id ON public.mt_doc_user_accounts USING btree ((data ->> 'providerName'), (user_id));

and from now on:
CREATE UNIQUE INDEX mt_doc_user_accounts_uidx_provider_nameuser_id ON public.mt_doc_user_accounts USING btree ((data ->> 'providerName'), (d.user_id));

[mysticmind]

This requires more fiddling, will take a look and fix the same. Sorry about this regression.

[mysticmind]

@aare-arnold this PR has been reverted and v8.2.1 released.