Linker script generation update

[tact1m4n3]

• multiple modes for linker script generation
• MemoryRegion update
• concatenate linker files directly in the generate linker script tool
• rp2xxx: use INSERT AFTER and INSERT BEFORE in linker scripts for additional sections
• esp: auto-generate memory regions in linker scripts
• esp: direct boot sections
• use the new .ram_text section instead of .time_critical in rp2xxx and .trap in esp. This section should always be placed in ram.
• rp2xxx: fix memory regions

[Grazfather]

Would be nice to have (even brief) documentation. design.md has a long-living TODO in there, maybe you can jot a few lines?

[tact1m4n3]

Would be nice to have (even brief) documentation. design.md has a long-living TODO in there, maybe you can jot a few lines?

Certainly. Also let's wait a bit on this PR. I've got to fix microzig_time_critical. I want to remove it from the automatically generated linker script as some chips have different memory regions mapped for code and data in ram. Also something similar I think happens for rodata (which I placed in flash by default :sob:).

[tact1m4n3]

Would be nice to have (even brief) documentation. design.md has a long-living TODO in there, maybe you can jot a few lines?

I added a brief insight into the system. Let me know what you think of it :)

[tact1m4n3]

You should consider adding to the dev log!

Are you referring to just use what I added in design.md? Or should I write something custom? Or a bit of both? :)

[mattnite]

@tact1m4n3 feel free to make it different but I say what you have there could be copy pasted, it's the perfect length!

[tact1m4n3]

Great! I'll add it then