[FEATURE] add alsa-utils and alsa-lib to SOF manifest

[kv2019i]

Is your feature request related to a problem? Please describe.
The SOF tools build uses alsatplg tool to build the binary tplg files from sources in SOF git.

Currently making changes that require change in alsatplg tool, need to be first merged to upstream alsa-utils,
then do an update of the SOF CI docker image, and only then a PR to SOF topology content can be submitted and tested.

Describe the solution you'd like
Add alsa-utils and alsa-lib to west manifest directly allowing to test draft version sof alsa-lib/alsa-utils changes and ensure correct version of alsatplg is used in topology builds. Original proposal from @lgirdwood in #9763 (comment)

Describe alternatives you've considered
Current BKM is to track docker updates with separate tickets, but this has proven to be slow and error prone:
#9790

Given the resulting binary tplg files do not encoding tool versioning information, it is very easy to have integration issues in case some alsatplg patch is missing in the tplg build.

Additional context

[kv2019i]

FYI to @singalsu @cgturner1 @ranj063 @udaymb

[teburd]

I think this is ok given the issue described. I've been thinking a lot more about west and dependency management as a whole lately as I've I think ran into some corners where west and the ideas behind it (repo) just aren't workable. This case though seems like it'd be ok to me.

[lgirdwood]

I think this is ok given the issue described. I've been thinking a lot more about west and dependency management as a whole lately as I've I think ran into some corners where west and the ideas behind it (repo) just aren't workable. This case though seems like it'd be ok to me.

Thanks @teburd - I will give this a try and discuss with you next time we chat.

[kv2019i]

Implemented with merging #9870

We have some downstream actions to update the docker images, but the main feature is now done and build scripts now use a locally installed alsa-lib/utils.