Support groups in inbound token accesslist

Summary

With inbound token accesslists becoming the default in 16.0, over the current outbound token accesslists, it would be very useful if the accesslist could contain a group and not just projects.

Where all projects in a group (which could be large) use tokens to trigger some common other project it would useful to add the whole group to the inbound accesslist instead of having to add dozens/hundreds of other projects individual to the list. This makes management of the accesslist much easier.

Particularly as the accesslist cannot currently be configured programmatically via Rest API. #351740 (closed)

Related to the inbound token accesslist feature:

#328553 (closed) #346298 (closed)

What is the current bug behavior?

Only individual projects can be added to the inbound token accesslist

What is the expected correct behavior?

Add a whole group to the inbound token accesslist