drivers: video: Add SMH option for video buffer

[LucasTambor]

This commit enables the user to choose whether to
allocate the video buffer from the video heap pool
or use a memory region with specific extra capabilities,
such as being cacheable/non-cacheable or using external
memory.

[zephyrbot]

The following west manifest projects have been modified in this Pull Request:

Name	Old Revision	New Revision	Diff

Note: This message is automatically posted and updated by the Manifest GitHub Action.

[epc-ake]

I was able to run it on the xiao_esp32s3 together with #75331 the changes from #74974 and the patch you send me on discord. 👍
However, I was not able to go above a resolution of 352x288 RGB565 before I run into <err> esp32_cam: DMA error: -32.
Which seems to be related with dma descriptors somehow... 😓
Also the issue with the generated overhead I mentioned here caused trough the dma_api really comes into play with higher video resolutions...

However, these issues most likely have nothing to do with this PR. So I'd call the test successful and try to fix the issues in the DMA and Video driver.

[LucasTambor]

@epc-ake The DMA error: -32 is related to the RX Watermark. Can you try increase gdma_ll_rx_set_water_mark and see if it helps?

[epc-ake]

@epc-ake The DMA error: -32 is related to the RX Watermark. Can you try increase gdma_ll_rx_set_water_mark and see if it helps?

Yes, this seems to fix it!
Can you maybe explain to me what gdma_ll_rx_set_water_mark does? Its not about the size of the dmas fifo, is it?
I needed to set it to 65. A value of 64 and lower didn't work and evan crashes the system with <err> os: ** CPU 0 EXCCAUSE 9 (load/store alignment)...
Now I'm able to capture the full 1600x1200 RGBA resolution 🚀

[LucasTambor]

@andyross @npitre