Naming of unit name concepts about uom HOT 2 CLOSED

Since we potentially want to move all the registries with global mutable state out of this package, it might be a good idea to keep symbol as-is on BaseUnit and AlternativeUnit and also keep the buildDerivedName function this package and export it for external use (it is a pure function that is not dependent on the registry). The function should be renamed to buildDerivedLabel or buildDerivedSymbol where the latter seems more logical since it uses the symbol field from the BaseUnit to build the result.

from uom.

Since buildDerivedName is a pure function with only Unit as input it makes sense to move that function to the unit.ts module and export it from there (and also rename it to buildDerivedSymbol).

from uom.