Use lower priority for block context filters

[dlh01]

Trac ticket: https://core.trac.wordpress.org/ticket/58699

[ockham]

Good catch; this admittedly didn't occur to me when working on WordPress/gutenberg#50313.

I think your solution makes sense; I was briefly debating whether we should use a slightly higher value (e.g. 5) for priority in order to allow other filters to kick in earlier, but I think it's true that from a backwards-compat point-of-view, using the lowest possible value is the closest we can get to retain the previous behavior.

However, this change will need to go "through" Gutenberg: As the e2e tests are flagging, blocks' dynamic PHP code is synced from the @wordpress/block-library npm package at build time in Core -- any changes made directly to that Code in Core will be flagged as a collision.

I'll go ahead and will file a GB PR 😊

[ockham]

One minor note: The docs say that

priorities are positive integers, typically between 1 and 20

Suggested change

	add_filter( 'render_block_context', $filter_block_context, 0 );
	add_filter( 'render_block_context', $filter_block_context, 1 );

[ockham]

I'll go ahead and will file a GB PR 😊

WordPress/gutenberg#52364

[ockham]

Per #4780 (comment), I'll go ahead and close this PR.

The suggested fix is over at WordPress/gutenberg#52364 😊