[DOCS] Cache busting if package is replaced

[maxtruxa]

If a package in a repository is replaced (or deleted and re-added), bpt continues to use the "old" version of the package if it's present in the local cache. This is totally understandable: How is bpt supposed to differentiate between the package revisions if they have the exact same version number (version+revision)?

I'm not sure if there is a good general solution for this. The obvious one is to never replace packages but always increment the version number (version and/or revision) instead. This aligns with what other package repositories (like PyPI and npm) are doing.
Packages can be replaced safely, if you have control over all downstream clients and can force them to clear their cache.

I don't think this is a huge issue, but should probably at least be mentioned somewhere in the docs for bpt repo.

[vector-of-bool]

This is indeed the purpose of the revision number: to bust client caches and force them to download a new package.

The docs don't make this clear, but it would be helpful to note this behavior.

[oraqlle]

How do you specify a revision to be imported to a CRS repository?