fix: Made options plugins effective

[TommyJackson85]

Related Issue

Closes #1177

Your solution

I just moved ...(options.plugins || []) to the bottom of the array.
@Pavel910 Am I right, in that this works becuase the Array is itterated through accendently from the start to the end, with Options essentially overwriting previous data / value changes from the other plugins callbacks?

How Has This Been Tested?

Will test this manually next.

Screenshots (if relevant):

None yet.

[TommyJackson85]

I haven't gotten around to testing this yet. Will try tomorrow, if not Sunday. If you need this done asap and feel confident in it though by all means set this for review and merge it!

[Pavel910]

@TommyJackson85 yes, when this whole array is passed to PluginsContainer it will take care of only using the latest registered plugin, so user-provided plugins will override the once that are built into the app template.

[TommyJackson85]

@Pavel910 the setup for testing my changes (from the issue page) is taking me a bit of time to set up, and I'm a little time restrained due to my regular job. So if you feel happy with this change, feel free to merge it anyway! Otherwise I will come back to this later in the week.

[Pavel910]

@TommyJackson85 thanks for reminding me, totally forgot about this as we are all over the place with the new stuff. Merging this, it's perfectly fine! 🚀 Thanks!