update --all may not get highest build number

[ReimarBauer]

updating with mamba of a project is much much faster than with conda only. :)

I can't say if conda or mamba would do this differently. I recognized on one of our servers that I had after the update --all the version 2.0.0 build number 0 while we have a build number 1.

Something blocked the update to go directly to 2.0.1. I've forced this by conda and updated based on that the other parts.

The most recent/highest build number is more important. We can't expect that a user knows how much builds from a software is available and how to get it.

our update procedure described:
Open-MSS/MSS#708 (comment)