Fix: set up builtins initial stack based on program builtins

Problem: when using `allow-missing-builtins` for a program, some
builtins requested by the program may not be part of the layout. This
results in an incorrect configuration of the initial stack of the
program as the program will expect pointers for all builtins, even
though it may not access them later down the line. An example of this
is any program that invokes another program (ex: the bootloader).

Solution: copy the Python VM implementation. We now iterate over the
program builtins and set the initial stack of the builtin if it is set
up in the VM and a default value of (0, 0) otherwise. When finalizing
the stack, we iterate over all Cairo builtins and decrement the stack
pointer if the builtin appears in the program and not in the layout.

CHANGELOG.md

@@ -2,6 +2,8 @@
 
 #### Upcoming Changes
 
+* fix: set up builtins initial stack based on program builtins [#1632](https://github.com/lambdaclass/cairo-vm/pull/1632)
+
 #### [1.0.0-rc1] - 2024-02-23
 
 * Bump `starknet-types-core` dependency version to 0.0.9 [#1628](https://github.com/lambdaclass/cairo-vm/pull/1628)