[TF-M] Why client API is built with tfm_sprt target?

Hi all,

I'm wondering why client API is build with tfm_sprt target (Secure Partition Runtime Library)? Client API is used by non-secure clients and secure clients. It means that static library is built once, but used with two different images. And it's expected that such images can use different types of cores, compilation settings, etc...

Probably it make sense to build this target in scope of psa_interface.

Regards, Roman.