Bridge admin access segregator

[mpetrun5]

• create a AccessControlSegregator contract to allow for per function address access for admin methods
• update Bridge to use AccessControlSegregator contract

Related Issue Or Context

Closes: #563

How Has This Been Tested? Testing details.

Unit tests.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation

Checklist:

• I have commented my code, particularly in hard-to-understand areas.
• I have ensured that all acceptance criteria (or expected behavior) from issue are met
• I have updated the documentation locally and in chainbridge-docs.
• I have added tests to cover my changes.
• I have ensured that all the checks are passing and green, I've signed the CLA bot

[lastperson]

Just realized that right now the relation between role and actor is one-to-one. Do we envision a situation where we might want multiple actors to have access to a function?

[mpetrun5]

Just realized that right now the relation between role and actor is one-to-one. Do we envision a situation where we might want multiple actors to have access to a function?

As far as I understand it is not a case that we planned to support, but I might be mistaken.
@P1sar

[P1sar]

Just realized that right now the relation between role and actor is one-to-one. Do we envision a situation where we might want multiple actors to have access to a function?

As far as I understand it is not a case that we planned to support, but I might be mistaken. @P1sar

Yes one role to one function is what we need