FEATURE: Fusion eel neos deprecation tracer

[mhsdesign]

Requires: neos/flow-development-collection#3386

Related: #4208
Related: #5022

Will by default log as "DEBUG" in development context hints if we use deprecated node field access:

24-09-24 18:39:26 97069      DEBUG                          The Node field "label" is deprecated in "${q(site).property('titleOverride') || site.label}"
24-09-24 18:39:26 97069      DEBUG                          The Node field "label" is deprecated in "${item.label}"
24-09-24 18:39:26 97069      DEBUG                          The Node field "identifier" is deprecated in "${node.identifier}"

Upgrade instructions

Review instructions

Checklist

• Code follows the PSR-2 coding style
• Tests have been created, run and adjusted as needed
• The PR is created against the lowest maintained branch
• Reviewer - PR Title is brief but complete and starts with FEATURE|TASK|BUGFIX
• Reviewer - The first section explains the change briefly for change-logs
• Reviewer - Breaking Changes are marked with !!! and have upgrade-instructions

[crydotsnake]

lol

[bwaidelich]

I like, thanks!

[dlubitz]

Looks good to me by reading.

But does this make sense, as long as we don't have any replacement for these in 8.4?

[dlubitz]

Tests are failing. Maybe a rebase is needed.

[mhsdesign]

Test are always failing on 8.4 :D ...

but you got a point regarding noes 8.4 vs 9.0 .... currently it doesnt look like well have replacements yet and maybe we should only log deprecations then if there is a replacement.... will retarget this pr for 9.0 and down merge that later ggf.