Allow priority to be set for Block and Inline Renderers

[SimonJulian]

Hi,

I noticed when trying to add a custom renderer that there was no way to pass a priority option through (meaning that if a renderer for the element type had already been registered and returned a non-null result, the renderer added to the config wouldn't be used).

This PR allows a priority key to be set for block / inline renderers, but falls back to 0 if not found. (0 is the default priority, so without adding the new key nothing should change),

I have also updated the comments in the config file to have the correct array key (class instead of blockClass) and bought the installation setup documentation page to be inline with the config file (as many of the comments were already out of date before I made my own changes to the config file).

As an complete aside, locally I went to run the tests just to be sure nothing I changed caused any issues, but I was getting a number of failures even when I reverted my changes and I'm really not sure why.

[freekmurze]

Thanks for your work on this!

Meanwile, I fixed the tests on main. Could you merge in that branch so we see if the tests would also pass on this PR?

[SimonJulian]

I've just done so, locally I'm still seeing 6 failures for some reason (which is a reduction from what I was seeing below).

I've attached the report.junit.xml that was generated as I wonder if something is odd my side but I'm not seeing anything oblivious.

report.junit.xml.txt

[freekmurze]

All checks seem to have passed on GitHub 👍