Add Version Constraint Resolution in fpm

[hridyasadanand]

Description

Feature Request: Add Version Constraint Resolution in fpm

Description:

• Problem: Currently, fpm does not allow users to specify version constraints for dependencies. This can cause compatibility issues when different versions of dependencies are required for various projects.
• Proposed Solution: Introduce version constraints in the fpm.toml configuration file. This would allow users to specify which versions of dependencies they want to use (e.g., >=1.2.0, <=2.0.0, or =1.5.0).
• Example Usage:

  [dependencies]
  dependency1 = ">=1.2.0"
  dependency2 = "=2.0.0"
  

Why this is important:

• Ensures that fpm projects are compatible with the correct versions of their dependencies.
• Helps developers avoid breaking changes caused by incompatible versions of dependencies.

Next Steps:

• Community discussion to confirm the design and implementation steps.

Possible Solution

No response

Additional Information

No response