Only throw lack of event key errors when we know we're in production

[jpwilliams]

Summary

Ensures that the "Failed to send event" error--produced when an event key has not been set on a client--will only throw in production environments and not local development.

This logic needed to change slightly anyway after the removal of INNGEST_DEVSERVER_URL in v3.

• If production detected, throw error if no event key
• If non-production detected, never throw an error (warning will still be shown upon instantiation)

Checklist

• [ ] Added a docs PR that references this PR N/A Bug fix
• [x] Added unit/integration tests
• [x] Added changesets if applicable

[changeset-bot[bot]]

🦋 Changeset detected

Latest commit: 5cff817b2037cacb4d3833059e731dcfd5e788f7

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

| Name | Type | | ------- | ----- | | inngest | Patch |

Not sure what this means? Click here to learn what changesets are.

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