Chore(mmu): add overflow handling

[4rgon4ut]

This PR add additional memory overflow detection(for both stack and heap).

Added:

• function to assert memory region where:
  1. zero padding region => stack overflow
  2. address higher than memory array length => heap overflow
  3. other not expected region => unknown mapping panic
• unit tests
• example to trigger stack && heap overflow in runtime

Closes: #395

[4rgon4ut]

I feel I need to get an acknowledgement for my direction as Im new to the codebase @moodlezoup.

1. Memory model:

Thus every attempt to write to zero_padding addresses is stack overflow and all writes over DRAM_BASE + memory.capacity is heap overflow. Is that correct?

2. It would be also nice to have sort of example program to face this cases in runtime. Is that something you would like to see?

3. store_raw() have no tracer call before actual operation, should I add checks in *_raw() functions?

[moodlezoup]

I feel I need to get an acknowledgement for my direction as Im new to the codebase @moodlezoup.

1. Memory model:

Thus every attempt to write to `zero_padding` addresses is stack overflow and all writes over `DRAM_BASE + memory.capacity` is heap overflow. Is that correct?

Yes this is correct

2. It would be also nice to have sort of example program to face this cases in runtime. Is that something you would like to see?

Yes, it would be great to have a test for this feature

3. store_raw() have no tracer call before actual operation, should I add checks in *_raw() functions?

I think so, but I haven't looked at that code in a while so if there's a better place to add the checks, go ahead

[4rgon4ut]

@moodlezoup

[moodlezoup]

Really nice work, thanks for adding the test cases!