Cleanup Agregation : replace dirty ref map with proper functional handling

type:fixed

Due to my laziness, I use a global ref map for generating new variables in Aggregation. This creates issues in another MR with a weird runtime pattern when running dune runtest because the table was filled with values from previous contracts which collide with the current contract.

This MR fixes the issue.

Changelog details:

fix a potential bug in the backend