Remappings versioning refactor

[mario-eth]

When a remapping is created, the name of the dependency should contain the version as well.
e.g.
@openzeppelin-4.9.0

This should be refactored to let the user choose what part of the versioning should be included:
major, major.minor, major.minor.patch, none

[beeb]

I guess this is somewhat mitigated by the fact that version requirement strings can be used to specify how dependencies are allowed to update. Example: 5 would allow versions >=5.0.0,<6.0.0, and the remappings would contain library-name-5.