Investigate if there are common patterns that should be implemented as 'mixins'

[leezen]

There are some common patterns that we might want to extract as function mixins or some other abstraction. This is distinct from #567 in that that seeks to build higher-level components, whereas we should see if there are any patterns (similar to the one described in #631) that we want to provide conveniences for.

[TechWatching]

Writing Pulumi code for RoleAssigment in Azure is not very convenient because the role definition id must be hardcoded after searching it in the documentation or computed at runtime using some mechanism (like here).

The code in C# for a RoleAssigment look likes the following:

        var storageReaderRole = new RoleAssignment("storageReader", new RoleAssignmentArgs
        {
            PrincipalId = functionApp.Identity.Apply(i => i.PrincipalId),
            PrincipalType = PrincipalType.ServicePrincipal,
            RoleDefinitionId = "/providers/Microsoft.Authorization/roleDefinitions/b7e6dc6d-f1e8-4753-8033-0f276bb0955b",
            Scope = storageAccount.Id
        });

I am pretty sure that these role definitions ids don't change over time so I guess it would be really easier to have an enum with all the role we can find in the documentation.