isbinaryfile does not follow semver for supported node, use fixed version

[mshima]

Use fixed version to avoid conflicts in the future

node v14 and v16 support were dropped in a patch version.

[SBoudrias]

Want to release this one and then do a major release with latest? I doubt we want to keep 14/16 compat going forward.

[mshima]

We already dropped node 14/16 in current major.

[mshima]

But this causes yeoman/yo#785 (comment) (the warning).

The fix would be to release mem-fs-editor v9 and v10 with isbinaryfile pinned at v5.0.0.

The PR is intended to don't have this problem again going forward.

[SBoudrias]

Ah I see. The problem IMO is it'll be a game of whack a mole, if not this dependency, it'll be another one or anywhere through another transitive dep. It's hard to maintain support outside LTS Node version. (no concern fixing this here, but in the grand scheme of things, I don't think it'll have a big impact on users)

[mshima]

Yes, I'm just avoiding breaking in the future, I don't plan to release another v9 and v10.