Add npm_and_yarn package managers' requirements to ecosystem metrics

[kbukum1]

What are you trying to accomplish?

This PR adds the ability to extract and report package manager version constraints for npm, pnpm, and yarn from the engines field in the package.json manifest file.

By including these constraints, the ecosystem metrics now provide better visibility into the range of supported package manager versions used in projects.

What issues does this affect or fix?

This PR enhances ecosystem metrics tracking for the npm_and_yarn ecosystem by introducing package manager version requirement collection and normalization for npm, pnpm, and yarn.

Anything you want to highlight for special attention from reviewers?

• Review the extraction logic for the engines field to ensure it handles constraints properly for npm, pnpm, and yarn.
• Validate that the conversion logic accurately transforms raw versions like 1.3.4 into =1.3.4.
• Consider edge cases where the engines field may contain incomplete or malformed version constraints.

How will you know you've accomplished your goal?

• The extracted package manager constraints for npm, pnpm, and yarn are correctly represented in the ecosystem metrics.
• All tests pass, including new tests that cover the extraction and conversion logic.
• The system handles invalid or edge-case engines fields gracefully.

Checklist

• I have run the complete test suite to ensure all tests and linters pass.
• I have thoroughly tested my code changes to ensure they work as expected, including adding additional tests for new functionality.
• I have written clear and descriptive commit messages.
• I have provided a detailed description of the changes in the pull request, including the problem it addresses, how it fixes the problem, and any relevant details about the implementation.
• I have ensured that the code is well-documented and easy to understand.

[abdulapopoola]

can you write the method names in full?

[kbukum1]

it is done.