Bluetooth: BAP: Broadcast Assistant API without src_id

[Thalley]

Summary

The broadcast assistant API for bt_bap_broadcast_assistant_mod_src, bt_bap_broadcast_assistant_set_broadcast_code and bt_bap_broadcast_assistant_rem_src rely on the src_id.

BAP defines a receive state as unique with the value tuple of {broadcast_id, addr_type, sid}. The broadcast assistant already implements broadcast_src_is_duplicate and is caching these values, so it is possible for the application to use the tuple instead of the src_id in order to perform actions.

If an application does not want to cache the src_ids to use the broadcast assistant API (or the CAP Commander API), but knows the broadcast information, then it may want to just supply that.

Describe the solution you'd like

The uniqueness of broadcast receive states based on the tuple can be used in 2 ways:

1. We can either modify the parameters to take either src_id or the above tuple, and perform the action, or we can create new APIs that takes the tuple rather than the src_id.

2. We can add a lookup function supplying the tuple and getting the src_id (and vice versa). Here it would also be possible to do a foreach function with a callback so that the application can implement this lookup

Alternatives

No response

Additional Context

No response