Do not hardcode the maximum global memory space

[vezenovm]

Problem

In #7021 for simplicity we hardcoded a MAX_GLOBAL_SPACE. This is used by both the GlobalSpace memory allocator and for determining the calldata start offset when copying calldata for the entry point. As we know globals at compile time we should be able to set the max memory allocated based upon the globals the user has specified.

Happy Case

There will be no hardcoded MAX_GLOBAL_SPACE and the memory allocated will be determined by the globals specified by the user.

Workaround

None

Workaround Description

No response

Additional Context

No response

Project Impact

Blocker

Blocker Context

This will block programs with a large amount of globals.

Would you like to submit a PR for this Issue?

None

Support Needs

No response