[MR Only] Edit any component prop, powered by a new FieldForComponentSuggester service, which will power the JS UI

Clarifying issue title.

Wim Leers → credited larowlan → .

Follow-up issues exist for out-of-scope but problems/todos surfaced here, with the exception of 2 that @larowlan graciously offered to create 🙏

(I did not implement the caching pieces @larowlan suggested, because it's too early to do add any caching — that only makes sense to add when the codebase is approaching its final shape, otherwise we risk premature optimization.)

CI is green.

Ready for final review.

This blocks ✨ [MR Only] Edit any component prop, powered by a new FieldForComponentSuggester service, which will power the JS UI Fixed .

And … here's a GIF showing it in action!

Wim Leers → credited f.mazeikis → .

RTBC: @f.mazeikis approved the MR. (This was the last issue that was created for an already in-progress MR, we'll default to issue forks going forward, which will be less confusing for Drupal contributors — at the cost of more confusing DX, which is fine!)

Given the very strong stabilizing impact of EndToEndDemoIntegrationTest, I don't want to wait to merge this until @larowlan also explicitly approves.

Having this in means next week will be more productive, because this test will serve as the https://en.wiktionary.org/wiki/canary_in_a_coal_mine for the data model/storage back-end infrastructure. 🐣

Also see @ctrlADel's write-up at #3452023-5: Research JSON schema forms for SDC configuration → , where he agrees with this direction even though he started out from a very different angle.

Automatically closed - issue fixed for 2 weeks with no activity.