Proposal to prioritise formulas in case the AppliedValue of a CostValue contradicts the Components

If a cost value has 2 components added together such that the AppliedValue should be 2+3=5, but the AppliedValue stores 6 instead, I propose to explicitly say that the formula results take priority.

In a viewer which does not calculate these things, it may display the AppliedValue, as 'reference' but not a source of truth.

In a more intelligent authoring software, capable of calculation, it should prioritise the formula. As such, if ArithmeticOperator is not NULL and there are components, then the formula shall be used whenever possible.

An alternative proposal is that the AppliedValue should be set to NULL if a formula is present. However, I think this is bad because it makes it less useful for viewers or simple import/export usecases.

As an example, with IfcTaskTime, the values (e.g. floats, late / early dates) that are calculated are explicitly described as "It is a calculated value." Perhaps we can add the same description to AppliedValue.