[FEATURE] Clean up SOF DMA interface(s)

[kv2019i]

Is your feature request related to a problem? Please describe.
DMA engines are key part of the SOF and the DMA interface are used in many place (to transfer audio data, to transfer payloads of IPC message, to implement trace, to implement debug features, and so forth).

As described in the commit message and documentation added in commit 816b143 , the transition to use native Zephyr DMA interface has been one of the complex transition tasks, and this work is not complete.

Describe the solution you'd like
This issue is used to track cleanup of the DMA usage in SOF application code with following goals:

• remove namespace overlap between SOF and Zephyr DMA APIs, making it clear which interface is used in application code (IOW, do not mix dma_ and DMA_ prefixes in definitions)
• retain support for transition interfaces (building SOF with Zephyr but with XTOS drivers), but move the related code to separate files and/or clearly separate namespace

Describe alternatives you've considered
One option is to wait for all targets to move to Zephyr (also to native drivers) and then DMA cleanup could be done by dropping all the legacy interfaces.

Additional context
Related to enhancement work done in #9015 and #5794

[kv2019i]

FYI @DINESHKUMARK1 -- this shouldn't interfere with work to enable Zephyr (#9549), but something to be aware of.

[lgirdwood]

May be easiest to do a xtos interface removal after we have all ported to Zephyr.

[lgirdwood]

Tagged for v2.12, some parts may be doable by this point, we can break down work if needed.