[2.0.0-beta1] Remove usage of setComponentSettingsExtra in field formatters in favor of injected contexts + Fix contexts issues + Fix ComponentFormatter issues

Ok, done.
I have added also some bonus :
- i fixed a bug in the context injected by field formatter, especially when used in views, where the bundle is unknown and set to empty string in our case.
- i refactored UI patterns views, to remove the existing service and use a trait for both row and style plugins. i fixed a few existing bugs in the codebase, especially related to view displays and default/overridden options.
- i added a new option to ViewRows source, that allows to use view rows as source, with a specific field only.

Demo with DSFR's tabs:

• The field formatter source doesn't show plugin form
• Duplicated & nested display
• Problem with context

Demo with Bootstrap's table:

• Undefined array key "#ajax_url" in Drupal\ui_patterns\Element\ComponentForm::buildPropsForm()
• Maybe this use case is not doable anyway because nested components in a single slot instead of single level component in 2 different slots

please test again, should be better ;)

pulled. And rebased from 2.0.x

During configuration

Seems OK but ComponentFormatter is available in the sources selector also for single value fields (like "title"). If selected, nothing happens. The plgin from is not displayed

After configuration, looking at the result

White screen of death:

TypeError: Drupal\ui_patterns_field_formatters\Plugin\Field\FieldFormatter\ComponentFormatterBase::checkContextSanity(): Argument #3 ($bundle) must be of type string, null given, called in modules/ui_patterns_field_formatters/src/Plugin/Field/FieldFormatter/ComponentFormatterBase.php on line 244 in Drupal\ui_patterns_field_formatters\Plugin\Field\FieldFormatter\ComponentFormatterBase->checkContextSanity() (line 282 of modules/ui_patterns_field_formatters/src/Plugin/Field/FieldFormatter/ComponentFormatterBase.php).

after testing more, adding a few new tests,
i did some improvements on other edge cases.
it is supposed to be fine now :)
please review Pierre.

adding tests is really cool, i think we need really a lot of them.

Hello,
i have updated a little bit the title and description of the issue, which is now solving more problems than initially expected...
MR is rebased and fully green now :)

Unfortunately, I will not be able to review today. you can merge yourself.