Exclude properties based on semver constraints

[W0rma]

Q	A
Bug fix?	no
New feature?	yes
Doc updated	yes
BC breaks?	no
Deprecations?	no
Tests pass?	yes
Fixed tickets	#1312
License	MIT

This PR adds the possibility to exclude properties from serialization based on version constraints accepted by composer.

Example:

use JMS\Serializer\Annotation\VersionConstraints;

class Author
{
    #[VersionConstraints('^6.1')]
    public function getAge(): int
    {
        return 61;
    }
}

I'm not sure if VersionConstraints is a good name or if there are better alternatives. Suggestions are welcome :)

[scyzoryck]

Thanks @W0rma for this PR! I left two minor comments.
Do you think that we should keep Until and Since attributes or they should be deprecated?

[W0rma]

Do you think that we should keep Until and Since attributes or they should be deprecated?

@scyzoryck Good point. I think they should be deprecated since version constraints provide even more flexibility. Do you agree?

[scyzoryck]

Thanks. Looks good to me.

I think they should be deprecated since version constraints provide even more flexibility. Do you agree?

It was my initial thought - as basically new constraint covers all functionalities provided by older constraints. On the other hand new one requires external dependency, so keeping simpler constraints might made sense too. @goetas - what do you think about it?

[goetas]

I would not abandon @Until and @Since , mainly for performance reasons. my guess is that composer/semver is way slower that the php's version_compare function, in a large object graph in it can make the difference.

I think that it could be also mentioned in the documentation the potential performance impact.

BTW, i would be curious to see a benchmark about it

[goetas]

what if this check is done in the metadata drivers? so we avoid to call it at runtime each time the annotation is instantiated?