fix: verify peer dependencies with error on load of package

[mjfaga]

Description

Follow-up to 6fb3e3b to ensure we don't leverage the library to validate it's loaded. Instead, we now load the verifyPeerDependencies module first and blow up with a clean error before starting to execute code.

[jdwyah]

@semanticart can you weigh in on this? This feels clearer / safer, but also friction annoyance on install. And i presume that this will make existing users that haven't needed a peer dependency to start failing after they update prefab-cloud-node.

My understanding is that many folks don't actually need this peer dependency / that this only rears its heads on some platforms. But is that wrong? If everybody need peer long then we can just add it to the docs. I'm unclear what the best idea is if this is only necessary sometimes. Maybe it's this.

[mjfaga]

Happy to also consider wrapping the entire module and only executing that check if the dependency is actually need. It will be a bunch more code, but would be manageable. Alternatively, I could spend time investigating the original issue and try to figure out why the package fails in certain environments, and then we can avoid this altogether maybe?