In the past, I have found that using Arduino CLI infrastructure for handling projects is not always the right choice
because Arduino CLI is intended to be resilient to sub-ideal project configurations when feasible, whereas Arduino Lint
is intended to enforce or encourage ideal project configurations.
However, Arduino Lint is not intended to lint the Library Manager index, so using Arduino CLI's code for querying the
index should be safe and avoid the problems associated with the code duplication that would be the alternative.

Arduino CLI and the Library Manager indexer has some provisional support for specifying version constraints in the
library.properties depends field. Although undocumented, this syntax is fully supported by the other tools, so Arduino
Lint's previous treatment of libraries using this feature as invalid is incorrect.

The library.properties depends field is used to specify the library dependencies. Although currently undocumented,
Arduino CLI and the Library Manager indexer both have provisional support for dependency version constraints.
Previously, LP048 did not have any support for the constraint syntax, which caused a spurious failure when they were in
use. This commit adds support for the constraint syntax and also causes the constraint information to be used when
checking if the dependency is provided by the index.