Add optional support for DT project-cloning REST API features that may require specific (or newer) recent versions of the server.
Note: not sure about "requiring" yet - so not throwing preliminary exceptions if a parameter was not None and the DT version was too old or unknown. At worst, the REST API call itself would return "not HTTP-200".
Part of the solution was to remember the last-reported version info from each (likely single) host when we get_dependencytrack_version()
Currently the version-parsing (from JSON into numbers) is done inside the one method that needs it. I can imagine it generalized to some more general parser if such fencing proves needed elsewhere in the future, and/or using the SemVer module or similar - to not reinvent a particularly complex wheel here :)
Add optional support for DT project-cloning REST API features that may require specific (or newer) recent versions of the server.
Noneand the DT version was too old or unknown. At worst, the REST API call itself would return "not HTTP-200".hostwhen weget_dependencytrack_version()