branchRuleUpdate mutation bug - unexpected AccesLevels results

Related to #441471 (closed)

There is some confusion about Access Levels Results in branchRuleUpdate

See comment for the details

We need to:

1. Add validations to ensure we users, groups, and deploy keys actually exist.
2. Hide the access level value for role based AccessLevels