feat(util-invariant): Convert to use util-logger under the hood

[lanceherman]

Description

This PR addresses issue #1488 by converting the util-invariant package to use util-logger under the hood instead of direct console.error calls.

Changes

• Converted util-invariant to use util-logger for logging
• Added optional logger level parameter to control logging behavior
• Maintained backward compatibility (defaults to error level and throwing)
• Added @onflow/util-logger as a dependency
• Fixed invalid type check in on-message-from-fcl.js

Implementation Details

• Default behavior remains the same (throws error) for backward compatibility
• New optional parameter allows changing logger level (e.g., to warning)
• When level is set to non-error, it prevents error throwing
• Fixed type checking issue in message handler

Testing

The changes maintain the existing functionality while adding the ability to:

• Use util-logger for consistent logging
• Optionally change log level
• Prevent error throwing when needed

Fixes #1488

[changeset-bot]

⚠️ No Changeset found

Latest commit: e89c424

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[lanceherman]

Hey @chasefleming could you review the changes and check if everything's alright. Thanks.

[lanceherman]

Hi @jribbink, thanks for the review!

The optional loggerLevel parameter was actually one of the specific requirements by @chasefleming in the original issue (#1488). From the issue description:

If syntax is the same, then default to util logger throwing an error
Add another arg that if set lets you change the logger level (e.g. to warning). This would also stop the throwing of the error.

That's why I implemented it this way:

By default (no logger level specified), it behaves exactly as before - throwing errors
The optional parameter allows changing to warning level, which was explicitly requested

[lanceherman]

hey @jribbink could you please review the changes.

[lanceherman]

hey @jribbink if you have time, please could you check if everything's alright