Implement set audio profile from demuxer

[CastagnaIT]

Description

The idea is use the "full codec string" (RFC 6381) to set the codec profile as hint from manifest data,
so that not influence decoders, then when start play the stream we set the right profile provided by demuxers.

fix #650

references used to implement Atmos signal as codec DD+ profile:
https://developer.apple.com/documentation/http-live-streaming/hls-authoring-specification-for-apple-devices-appendixes
https://ott.dolby.com/OnDelKits/DDP/Dolby_Digital_Plus_Online_Delivery_Kit_v1.5/Documentation/Content_Creation/SDM/help_files/topics/ddp_mpeg_dash_c_signal_atmos_in_isobmf_2.html

Smooth streaming manifest case
this manifest works differents and its more complex find a good solution due to handmade Movie Atoms,
so its use CSession::CreateMovieAtom to allow CFragmentedSampleReader to determinate codec type,
but currently create an appropriate audio SampleDescription require some code reworks and will not be considered here.
This means that for now smooth streaming cases there are no codec profiles.

This PR depends from xbmc PR's:
xbmc/xbmc#23524
xbmc/xbmc#23541

BEFORE

AFTER

Motivation and context

Set the missing audio profile and allow distinguish from kodi GUI audio track list the type of codec since multiple tracks could have same characteristics with same language, but different codec quality

How has this been tested?

For HLS, following sample include most common audio codec types included atmos:
https://devstreaming-cdn.apple.com/videos/streaming/examples/adv_dv_atmos/main.m3u8

Smooth streaming, no changes, read note in description

DASH Atmos: https://ott.dolby.com/OnDelKits/DDP/Dolby_Digital_Plus_Online_Delivery_Kit_v1.4.1/Test_Signals/muxed_streams/DASH/OnDemand_MPD/ChID_voices_1280x720p_25fps_h264_6ch_640kbps_ddp_joc.mpd

Screenshots (if appropriate):

Types of change

• Bug fix (non-breaking change which fixes an issue)
• Clean up (non-breaking change which removes non-working, unmaintained functionality)
• Improvement (non-breaking change which improves existing functionality)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that will cause existing functionality to change)
• Cosmetic change (non-breaking change that doesn't touch code)
• None of the above (please explain below)

Checklist:

• I have read the Contributing document
• My code follows the Code Guidelines of this project
• My change requires a change to the Wiki documentation
• I have updated the documentation accordingly

[CastagnaIT]

@glennguy in awaiting that xbmc PR's are merged, you can prepare review

[glennguy]

Looks good!