Generalised (Root Origin) Extrinsic Execution Proposal

Background

Currently, all proposals are hard-coded to execute a specific codepath, with hard-coded proposal parameters. If the council is to be able to control new parts of the runtime, for which there is no proposal, a new proposal has to be manually introduced.

Proposal

Our current approach is very safe, however, the ability to do generalized extrinsic invocation, even with Root Origin, can allow us to avoid introducing new proposals for every possible action, such as setting parameters, that we may want to do. By having this this action be wrapped in a specific proposal with proposal parameters equivalent to a Runtime upgrade, we do not sacrifice any security, but we make it easy for the council to manage the runtime in a no-code way as the runtime changes.

NB: only a single call should be allowed though, unless this problem has somehow been resolved https://github.com/Joystream/joystream/issues/4187

┆Issue is synchronized with this Asana task by Unito

Start by reviewing the existing hard-coded proposal execution paths and the constraint described in issue #4187. Define the scope and safety requirements for a generalized Root Origin extrinsic proposal, including the single-call restriction; done requires an agreed design that avoids adding a proposal for each runtime action.