Revert "Reintroduce translation of identifiers to Protobuf compliant names (#3736)"

[alecgrieser]

This reverts commit 4873b51 (PR #3736) in response to some issues seen with how this may result in the planner failing to produce a query for some queries. The exact circumstances required for this are still under investigation, so rather than fix the bug, this reverts the renaming change.

[github-actions]

📊 Metrics Diff Analysis Report

Summary

• New queries: 0
• Dropped queries: 50
• Plan changed + metrics changed: 0
• Plan unchanged + metrics changed: 0

ℹ️ About this analysis

This automated analysis compares query planner metrics between the base branch and this PR. It categorizes changes into:

• New queries: Queries added in this PR
• Dropped queries: Queries removed in this PR. These should be reviewed to ensure we are not losing coverage.
• Plan changed + metrics changed: The query plan has changed along with planner metrics.
• Metrics only changed: Same plan but different metrics

The last category in particular may indicate planner regressions that should be investigated.

Dropped Queries

The following queries with metrics were removed:

• yaml-tests/src/test/resources/valid-identifiers.metrics.yaml:2: EXPLAIN select "foo.tableA".* from "foo.tableA";
• yaml-tests/src/test/resources/valid-identifiers.metrics.yaml:14: EXPLAIN select * from "foo.tableA";
• yaml-tests/src/test/resources/valid-identifiers.metrics.yaml:26: EXPLAIN select "_$$$".* from "foo.tableA" as "_$$$";
• yaml-tests/src/test/resources/valid-identifiers.metrics.yaml:38: EXPLAIN select "foo.tableA.A2", sum("foo.tableA.A1") from "foo.tableA" group by "foo.tableA.A2";
• yaml-tests/src/test/resources/valid-identifiers.metrics.yaml:50: EXPLAIN select * from "foo.tableA", "foo.tableB" where "foo.tableA"."foo.tableA.A1" = "foo.tableB"."foo.tableB.B1";
• yaml-tests/src/test/resources/valid-identifiers.metrics.yaml:65: EXPLAIN select "foo$tableC$C2", sum("foo$tableC$C1") from "foo$tableC" group by "foo$tableC$C2";
• yaml-tests/src/test/resources/valid-identifiers.metrics.yaml:77: EXPLAIN select "__foo__tableD".* from "__foo__tableD";
• yaml-tests/src/test/resources/valid-identifiers.metrics.yaml:89: EXPLAIN select "__foo__tableD".* from "__foo__tableD" where "__foo__tableD$D3" >= 2;
• yaml-tests/src/test/resources/valid-identifiers.metrics.yaml:103: EXPLAIN select "__foo__tableD"."__foo__tableD$D1" from "__foo__tableD";
• yaml-tests/src/test/resources/valid-identifiers.metrics.yaml:114: EXPLAIN select "__foo__tableD$D1" from "__foo__tableD";
• yaml-tests/src/test/resources/valid-identifiers.metrics.yaml:125: EXPLAIN select "__foo__tableD".* from "__foo__tableD" where "__foo__tableD$D3" >= 2 order by "__foo__tableD$D1";
• yaml-tests/src/test/resources/valid-identifiers.metrics.yaml:139: EXPLAIN select "βήτα__f"("f__e"."foo.tableE.E3") AS "___h.1" from "foo.tableE" as "f__e" where "alpha__f"("f__e"."foo.tableE.E3") = 5
• yaml-tests/src/test/resources/valid-identifiers.metrics.yaml:151: EXPLAIN select "alpha__f"("f__e"."foo.tableE.E3") AS "___h.1" from "foo.tableE" as "f__e" where "βήτα__f"("f__e"."foo.tableE.E3") >= 50
• yaml-tests/src/test/resources/valid-identifiers.metrics.yaml:163: EXPLAIN select * from "__$func3"(10, 1, 1);
• yaml-tests/src/test/resources/valid-identifiers.metrics.yaml:177: EXPLAIN select * from "$yay"(5);
• yaml-tests/src/test/resources/valid-identifiers.metrics.yaml:188: EXPLAIN select * from "__2yay"(6);
• yaml-tests/src/test/resources/valid-identifiers.metrics.yaml:199: EXPLAIN select * from "नमस्त"(4);
• yaml-tests/src/test/resources/valid-identifiers.metrics.yaml:210: EXPLAIN select * from "$yay__view";
• yaml-tests/src/test/resources/valid-identifiers.metrics.yaml:221: EXPLAIN select * from "__2yay__view";
• yaml-tests/src/test/resources/valid-identifiers.metrics.yaml:232: EXPLAIN select * from "வணக்கம்";

This list has been truncated. There are 30 remaining dropped queries.

The reviewer should double check that these queries were removed intentionally to avoid a loss of coverage.

[alecgrieser]

The test gaps are for methods that I modified as part of the PR. There are tests of what the new behavior is, but I can't take out the old behavior cleanly and introduce new tests. I'm proposing we bypass that check and merge anyway given the situation