feat: add logger.hasErrorLogged(error) method

[aleclarson]

Description

This makes it easier for frameworks which wrap Vite (eg: vite-plugin-ssr) to avoid logging an error that was already logged by Vite.

Additional context

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the Commit Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

[yyx990803]

Let's pass the error to logger.error as part of the options and do the marking inside logger.error

[aleclarson]

I've added the logger.hasLogged method, and the error option must be defined by callers of logger.error. They can pass error: null if no associated error exists. This ensures the option isn't forgotten about.

That makes this PR a breaking change.

In Vite itself, most logged errors are not rethrown, so marking them is pointless, but I'm passing the Error object whenever possible as a principle.

[patak-dev]

I see that there is a comment about a breaking change, @antfu is this safe to merge in the 2.5 beta? We'll do a beta-1 today so we could still include this one

[antfu]

I have changed the options argument to optional to avoid breaking changes.