use esc_url() for the term link href in get_the_taxonomies()

[nvxbug]

Failing assertion when a term_link filter returns a javascript: URL:

Failed asserting that 'Categories: <a href="javascript:alert(1)">Uncategorized</a>.'
does not contain "javascript:".

get_the_taxonomies() builds the term href with esc_attr( get_term_link( $term ) ). esc_attr() does not apply the protocol allowlist, so a scheme injected through the public term_link filter reaches the anchor unchanged. The sibling renderers get_the_term_list() and get_the_category_list() already run the same value through esc_url(); this brings get_the_taxonomies() in line with them. Included a regression test that fails on the current code and passes with the change.

Trac ticket:

[github-actions]

Trac Ticket Missing

This pull request is missing a link to a Trac ticket. For a contribution to be considered, there must be a corresponding ticket in Trac.

To attach a pull request to a Trac ticket, please include the ticket's full URL in your pull request description. More information about contributing to WordPress on GitHub can be found in the Core Handbook.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @nvxbug.

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.