Fix small problem with schema name in page titles

[seancolsen]

This PR rips out some weird low-level code that was inserting the schema name into HTML page <title> elements whenever possible. This code came to my attention because of the TODO_BETA comment, but upon closer inspection, I noticed that it was causing this subtle (and low impact) bug where the schema name is included twice in the schema page:

Much to my chagrin, apparently I wrote this logic back on 2022-09-20. But yuck, I do not like that! If we want the schema name to be in page titles, we ought to be setting that at a higher level, like here, where on some pages we know we have a schema and on other pages we know we do not have a schema. All in all, I don't think we actually need to worry about include the shcema name in page titles.

This PR simplifies things, removes the TODO_BETA comment, and fixes the bug. It does mean that table pages and record pages will no longer include the shcema name, but I don't think that's a problem.

Checklist

• My pull request has a descriptive title (not a vague title like Update index.md).
• My pull request targets the develop branch of the repository
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added tests for the changes I made (if applicable).
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.