fix: drop version check as it seems to be not needed

[sakulstra]

The current version check doesn't work with two digit minor/major release numbers breaking at 1.10.x
As I didn't see a good reason to have this check in first place I dropped it

• closes Meteor release validation #17

---

I also noticed that package.json enforces:

"engines": {
    "node": ">=4"
  }

could/should we update this to >=8/10?
10 because that's the oldest still supported node version
8 because a lot of people are still on meteor 1.8 😅

[CLAassistant]

All committers have signed the CLA.

[ramijarrar]

I also noticed that package.json enforces:

"engines": {
    "node": ">=4"
  }

could/should we update this to >=8/10?
10 because that's the oldest still supported node version
8 because a lot of people are still on meteor 1.8 😅

Probably a good idea as many of the project dependencies will no longer transpile for Node <8 (also it's only an informational flag so nothing will stop working for existing users).

Meteor 1.8 users can still use v12+ to run the CLI globally as the Node/NPM versions are parsed from the Meteor CLI: https://github.com/EducationLink/meteor-google-cloud/blob/cb72dca6ab970ddf841f7c223ac665c6ad44fbf6/src/lib/google.js#L51-L58

[sakulstra]

@ramijarrar anything else i should do to push this forward?
opened another pr for the version update as I didn't want to delay the release of this pr

[ramijarrar]

@sakulstra I'm not actually a maintainer of this repo 😄 (it was inspired by my Meteor Azure integration so I chimed in when I noticed the issue carried over)