Align block structure with yellow paper

[LHerskind]

The block as defined currently is very hard to follow. It uses different names all over the place to refer to the same things. We should use structs when possible, and be more consistent in the naming.

For example, the L2Block don't explicitly define the block header, so the BlockHeader in typescript is not consistent with the actual block. It is only the "after" half of it.

Instead, we must update it to match what is described in the yellow-paper.

### Tasks
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/3572
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/3589
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/3592
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/3916
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/3820
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/3936
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/4010
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/4011
- [x] Restructure the API's to fetch "header" instead of individual parts and then building anyway
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/3868
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/3938
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/3849
- [ ] Update L1 state root definition (pedersen or sha)
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/3824
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/3937
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/3941
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/4031
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/4045
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/4134
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/3441
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/4720

[LHerskind]

The blocksTreeRoot also is a bad name, hence it is not actually a tree of blocks, but a tree of StateContext from the above definitions (almost).

It should either be renamed, or consist of commitments to the actual blocks.

Our apis which are mostly used for building the header should also be altered to return a StateReference instead and header building should be more easily exposed to the PXE.

[LHerskind]

From discussion earlier, we came up with a few structs and hopefully some better naming:

// Base rollup only change part of the state
interface PartialStateReference {
    noteHashTreeRoot: Snapshot;
    nullifierTreeRoot: Snapshot;
    contractTreeRoot: Snapshot;
    publicDataTreeRoot: Fr;
};

// StateRoot = H(StateReference)
// Tree of StateRoots = Archive
interface StateReference {
    ...partialStateReference;
    privateKernelVkTreeRoot: Snapshot;
    l1ToL2MessageTreeRoot: Snapshot; 
    archiveRoot: Fr; // Before insertion of this leaf
    globalVariablesHash: H(GlobalVariables);
};

interface CombinedConstantData {
    historical_state: StateReference; // old header
    context: TxContext;
};

interface BlockHeader {
    parent: StateRoot;
    state: StateReference;
    globalVariables: GlobalVariables;
}

interface Block {
    header: BlockHeader;
    content: Content;
}

Further, there are some cleanup to do regarding global variables which have multiple variations in noir which makes it hard to follow.

[LHerskind]

As mentioned in #3564 it will also be useful to expose the block number as part of the state reference to make historic access easier. Practically, this could be done by not providing a globalVariablesHash but actually provide the global variables, that way we can just read them directly, and as we are not in the getting all the juice out of the circuits state, this seems like a valid route to make it easier to understand what is going on and build.