feat: use Felt directly instead of Felt252 alias

[eeemmmmmm]

TITLE

feat: use Felt directly instead of Felt252 alias

Description

Implements a simple but important change: using the standardized Felt type directly from starknet_types_core instead of aliasing it as Felt252.

The change is minimal but strategic - it adds a backward-compatible type alias while setting the foundation for future code to use the proper Felt type. This aligns cairo-vm with the broader Starknet ecosystem's standardization efforts.

Description of the pull request changes and motivation.

Checklist

• Linked to Github Issue
• Unit tests added
• Integration tests added.
• This change requires new documentation.
  • Documentation has been added/updated.
  • CHANGELOG has been updated.

[gabrielbosio]

Hi @eeemmmmmm, I am curious to know what project needs to use this alias so that we are sure we are not adding something to the VM API that is not used by anyone

[eeemmmmmm]

Hey @gabrielbosio, this change improves code clarity by using the direct type name Felt while maintaining backward compatibility with a Felt252 type alias. The alias ensures existing code continues to work without changes while allowing new code to use the more straightforward name

[eeemmmmmm]

To answer your question: The Felt252 alias is widely used throughout the cairo-vm codebase itself. The alias maintains API stability for all existing code while allowing new code to use the more intuitive name.

[gabrielbosio]

I realized that I have mixed terms... What I meant is if there is a project that needs to use the felt type from the VM using the original name Felt instead of the Felt252 alias (One reason I think of is for name consistency with other dependencies, but I am curious if there is a concrete use case).