Parse negative values for numeric parser types

[Jaksenc]

Summary

• recognize parseInt and parseFloat as numeric parser types when deciding whether a required option may consume a following negative-looking value
• carry the same numeric metadata through array parser specs, so [Number] and [parseInt] handle separate negative values consistently
• preserve strict option parsing for non-numeric-looking tokens such as -abc and for non-numeric option types such as String

This keeps the existing negative-number exception narrow instead of making every required option consume the next dash-prefixed token.

Fixes #52.

Verification

• npm test
• npx prettier --check index.js test.js
• git diff --check
• node --check index.js
• npx -p node@20 node node_modules/jest/bin/jest.js --coverage -w 2