When a main administrator gives a new collaborator access to certain branches (for example: only epel branches), it is not possible for most users to see the exact settings in the Pagure dist-git web UI.

For example, @gsauthof gave me permission to epel8 for python-asyncssh, but when I push there, Pagure says access denied. I cannot see what regex @gsauthof used, or anything that would indicate that my branch settings are restricted: https://src.fedoraproject.org/rpms/python-asyncssh

Steps to reproduce:

1. Add a user as a collaborator to a package's repo
2. Restrict the branches that new collaborator may access
3. The collaborator gets "access denied" to a branch, and needs to debug the
   settings.

Actual Results:
Only admins can see the branches setting in place for a collaborator by clicking "settings".
No collaborators or public users can see the branch settings on a package.

Expected Results
Anyone including anonymous users can see the branch settings for all packages in the web UI.

Additional Info:
Users can view the information by reading the API docs and guessing at REST API endpoints. The information is not available in the main "project" endpoint (eg. /api/0/rpms/<package>). It is available in the /api/0/rpms/<package>/contributors endpoint, eg. https://src.fedoraproject.org/api/0/rpms/python-asyncssh/contributors