adding trailing slashes in BaseLink

[x] Include a description of your pull request and instructions for the reviewer to verify your work.
[ ] Link to the issue if this PR is issue-specific.
[ ] Create/update the corresponding story if this includes a UI component.
[ ] Create/update documentation. If not included, tell us why.
[ ] List the environments / browsers in which you tested your changes.
[ ] Tests, linting, or other required checks are passing.
[ ] PR has an informative and human-readable title
- PR titles are used to generate the change log in releases; good ones make that easier to scan.
- PRs will be broadly categorized in the change log, but for even easier scanning, consider prefixing with a component name or other useful categorization, e.g., "BaseButton: fix layout bug", or "Storybook: Update dependencies".
[ ] PR has been tagged with a SemVer label and a general category label, or skip-changelog.
- These tags are used to do the aforementioned broad categorization in the change log and determine what the next release's version number should be.
- Release Drafter will attempt to do the category labeling for you! Please double-check its work.

Description

Supports:

Adds a trailing slash to all links regardless if it's a router link or not. Checks urls for files and query params.

Not testable in Storybook as we use a mock component for NuxtLink. Best way to test is in www. To do this locally:

in www, replaced the @explorer-1 packages in /apps/frontend/package.json with the paths in /README.md
pnpm i
make frontend-local