Fix/ab#76765 calculated fields not working in aggregation parent form

[RenzoPrats]

Description

Fixed calculated field not working in an aggregation and layout of parent form.

Useful links

ticket

Type of change

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

It has been tested creating a form child and then a parent form using the form child as a resource question, after that was created calculated fields in the child resource and finally was created aggregations and layouts of the parent resource using the calculated fields of the child.

Screenshots

Checklist:

( * == Mandatory )

• * I have set myself as assignee of the pull request
• * My code follows the style guidelines of this project
• * Linting does not generate new warnings
• * I have performed a self-review of my own code
• * I have put the ticket for review, adding the oort-backend team to the list of reviewers
• * I have commented my code, particularly in hard-to-understand areas
• * I have put JSDoc comment in all required places
• * My changes generate no new warnings
• * I have included screenshots describing my changes if relevant
• * I have selected labels in the Pull Request, according to the changes with code brings
• I have made corresponding changes to the documentation ( if required )
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[MwanPygmay]

@RenzoPrats, not working, tested with calc field {{calc.if( {{calc.eq( {{data.number}} ; 12 )}} ; 30 ; {{data.number}} )}}.

from above, I think you are missing some steps for unnesting.