Staff permissions are not enough to create/edit/delete builds in Capomastro

[Caio Begotti]

As of today anyone who needs to create or edit or delete a build (be it a project or a dependency one) need Django's superuser powers to do so. The staff permissions, which I would expect to be enough for this, is not used at all and is handled exactly the same as regular users in Capomastro. We would need to tweak this to allow a fine-grained control of accounts so different access levels are actually respected.

[Daniel Manrique (roadmr)]

Looks like all the permissions infrastructure is in place, we need to add permissions checking in the proper views/models. This is well-described so setting to triaged.