Feature/load and run script

[EdwardLarson]

• [X] I have reviewed the OFRAK contributor guide and attest that this pull request is in accordance with it.

One sentence summary of this PR (This should go in the CHANGELOG!) Add a Modifier and associated GUI button/view to upload a Python file and run a function in that file on the selected Resource

Link to Related Issue(s)

Please describe the changes in your request.

TODO:

• [x] Write a test for the Modifier
• [x] Custom icon for the "Run Script" button
• [x] Clean up the CSS to make the "Run Script" view tolerable

Anyone you think should look at this, specifically?

[EdwardLarson]

@whyitfor What do you think of gating this behind the "Experimental Features" checkbox? We were talking about it at standup today, and all of us could go either way.

On the one hand, in some ways it is simpler than running any component, since we only need one simple config to be properly serialized/deserialized. On the other hand, there could be a lot of "weird" side effects running scripts.

[marczalik]

@whyitfor What do you think of gating this behind the "Experimental Features" checkbox? We were talking about it at standup today, and all of us could go either way.

On the one hand, in some ways it is simpler than running any component, since we only need one simple config to be properly serialized/deserialized. On the other hand, there could be a lot of "weird" side effects running scripts.

@EdwardLarson As mentioned offline, if we know that the UI/UX will change significantly for this feature that may be a good reason to set it behind "Experimental Features" for now. Regarding the fact that it's not an API-level change, I still think it's a good idea to inform users ahead of time if we know that something is being shipped "unfinished" and that seems like what "Experimental Features" should be.

[whyitfor]

@EdwardLarson, if we are on the fence then let's put it behind the "experimental" config.