fix: use accurate test links in HTML reporter

[danny0838]

PR Checklist

• Addresses an existing open issue: fixes 🐛 Bug: suite/test links for HTML reporter may hit unrelated tests #5232
• That issue was marked as status: accepting prs
• Steps in CONTRIBUTING.md were taken

Overview

Fix inaccurate suite/test links that may hit unrelated tests:

• Add '^' and ' ' for a suite link so that a link for Case1 won't hit Case10 test1.
• Add '^' and '$' for a test link so that a link for CSS won't hit should fix invalid CSS.

[JoshuaKGoldberg]

• Steps in CONTRIBUTING.md were taken

I don't think they were 🙂. From that doc:

• Please file an issue using the feature request template if you have a change to propose, including a bugfix.
• Unit and/or integration tests are required for any code change.

As maintainers looking at this PR, we don't know what bugs you're suggesting this PR will fix, why it fixes them, or what test cases would be needed to enforce that they stay fixed. I appreciate the drive to improve things in Mocha (thanks!) but please follow the contributing guide. Switching to a draft PR in the meantime.

[danny0838]

It should already be quite clear in the Overview section as well as in the commit message: this PR is to fix inaccurate test links for the HTML reporter, such as clicking on a link for describe('Case1') would get a query that hits unwanted describe('Case10', function () { it('test1') }), or clicking on a link for it('CSS') would get a query that hits unwanted it('should fix invalid CSS').

As for tests: this is a UI-related change and I wonder how and what test you would like it to be? Look back the commit history, many previous changes about the reporter didn't have related tests, such as e263c7a. If you really want a test then I think it either has to be run manually, or you'd have to implement a whole ecosystem for headless-browser related tests.