feat: use context-based role assignments to implement the permission model

[hiddentao]

Notes:

• All new ACL that allows for context-based role setting and other fun features. Fully tested!
• The transfer lock is complex to do using roles because it would require going into the ERC1155 too to handle approvals etc. So I opted for a flag instead for that one.

[coveralls]

Pull Request Test Coverage Report for Build 13712517344

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 94 of 180 (52.22%) changed or added relevant lines in 8 files are covered.
• 4 unchanged lines in 2 files lost coverage.
• Overall coverage decreased (-3.2%) to 54.758%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
contracts/src/registry/RootRegistry.sol	2	3	66.67%
contracts/src/registry/PermissionedRegistry.sol	2	4	50.0%
contracts/src/registry/NameWrapperRegistry.sol	0	83	0.0%

Files with Coverage Reduction	New Missed Lines	%
contracts/src/registry/RootRegistry.sol	1	75.0%
contracts/src/registry/PermissionedRegistry.sol	3	73.68%

Totals
Change from base Build 13351832110:	-3.2%
Covered Lines:	278
Relevant Lines:	495

---

💛 - Coveralls

[Arachnid]

Does this mean that if you emancipate a name, it's no longer possible to grant the owner permission to renew it?

[hiddentao]

Yes, because in the name wrapper, once you emancipate you can no longer burn any other fuses on it. That was my interpretation.

[Arachnid]

The parent owner cannot - but if I'm reading this correctly, the emancipated owner cannot renew either!

[hiddentao]

@Arachnid Given that we only need to transfer two roles to a new registrar (registrar and renew) I felt that it was easier to do that manually whilst keeping the current storage approach in EnhancedAccessControl, i.e. not using a bitmap. Even if we use a Bitmap then keeping the "revoke all assignments of this role within this resource" O(1) feature would still require versioning of assignments, meaning that we'd still be doing a lot of complex storage work in access control.

Plus, role transfers only work across a particular context. There's no way to transfer all of a user's roles in all contexts. I suppose if we implement hierarchical contexts of some sort we could perhaps do this. But again, this complicates the access control storage.

Happy to discuss this further over calls.