Migrate Calculations to DX

[toropok]

Description of the issue/feature this PR addresses

This PR migrates the AT Calculation to Dexterity for Python 3 compatibility.

Current behavior before PR

Calculation is a content type based on the Archetypes framework

Desired behavior after PR is merged

Calculation is a content type based on the Dexterity framework

--
I confirm I have tested this PR thoroughly and coded it according to PEP8
and Plone's Python styleguide standards.

[xispa]

Excellent work @toropok and @Bugerman58 🥇 . I can imagine how challenging the migration of Calculation has been!. Your amazing work is really appreciated! Willing to review the Pull Request already and maybe we open another one later for the removal of the HistoryAware relic!

[xispa]

Hi @toropok , tests are failing https://github.com/senaite/senaite.core/actions/runs/11948903328/job/33307294669

Can you please take a look before I start to review?

[toropok]

Hi @toropok , tests are failing https://github.com/senaite/senaite.core/actions/runs/11948903328/job/33307294669

Can you please take a look before I start to review?

Hi @xispa

Sure, I'll fix the failed Python tests (they only test object validation) and get back to you. The remaining failing tests are doctests, which are related to HistoryAwareReferenceField.

[toropok]

@xispa

Sorry for the long pause.

• I’ve added FormulaValidator, and it works! 🙂
• Fixed the Python tests — all tests are now passing successfully.

That leaves us with two remaining issues that need your guidance and vision:

1. HistoryAware behavior for UIDReferenceField: All the failing doctests are related to this feature.
2. Formula wildcards: How are they supposed to work? It seems like they’ve never worked as intended.

[xispa]

Pheew, a lot of work here... @toropok you must be exhausted. I've done a first review and requested some changes though.

Haven't gone through the validators details yet, but I think you can simplify a lot there. I feel are overwhelming, will review them in the next round.

I've seen tests that are failing are because of the HistoryAwareReferenceField. Don't worry too much about this for now.

[xispa]

1. HistoryAware behavior for UIDReferenceField: All the failing doctests are related to this feature.

Yes, I've seen. I've requested some changes, we will handle this HistoryAware behavior afterwards.

2. Formula wildcards: How are they supposed to work? It seems like they’ve never worked as intended.

They are supposed to work, yes. For instance, if the user types this formula:

[CHOL] + [FAT] if [CHOL] >= [CHOL.LDL] else "Invalid"

where:

• CHOL is the keyword of a service (e.g. Cholesterol)
• FAT is the keyword of a saervice (e.g. Fat)
• <service_keyword>.LDL is the wildcard representing the value of the field LowerDetectionLimit for the prefixed service

Therefore, if the result of CHOL is below the LowerDetectionLimit, the result of the calculation will be Invalid.

See e.g. the doctests here: https://github.com/senaite/senaite.core/blob/2.x/src/senaite/core/tests/test_calculations.py#L83-L137

[toropok]

They are supposed to work, yes. For instance, if the user types this formula:

Yeah, I see now. But it's never worked before for calculating test results with wildcards used at least