Failing kernel tests for all ways a component source can fail to render on the server side

Overview

This is blocked by #3501290: Introduce unit test coverage for both ComponentSource plugins (Block + SDC).
This blocks #3485878: Server-rendered component instances should NEVER result in a user-facing error, should fall back to a meaningful error instead (+ log).

Implement explicit kernel tests for 5 of the 6 acceptance criteria at #3517941: [META] Robust component instance error handling during hydration+rendering.

1. A Drupal Block plugin (whose rendering logic throws a PHP exception) used as a component instance in an XB component tree does NOT make the rest of the component tree unusable.
2. An SDC (whose Twig logic throws a PHP exception) used as a component instance in an XB component tree does NOT make the rest of the component tree unusable (except that if this SDC has slots, those slots MAY not appear in the preview , but they would appear in the “Layers” view 👈 out of scope to test here).
3. A code component (whose JS logic throws a JS exception) used as a component instance whose explicit inputs are invalid does NOT make the rest of the component tree unusable (except that if this code component has slots, those slots MAY not appear in the preview, but they would appear in the “Layers” view). 👈 out of scope to test here
4. A Drupal Block plugin used as a component instance whose explicit inputs are invalid does NOT make the rest of the component tree unusable.
5. An SDC used as a component instance whose explicit inputs are invalid does NOT make the rest of the component tree unusable.
6. A code component used as a component instance whose explicit inputs are invalid does NOT make the rest of the component tree unusable.

Proposed resolution

1. Create a crash SDC in the xb_test_sdc module, which accepts a type: boolean "crash" prop which will cause the Twig to trigger a PHP exception. This is for criterium 2.
2. Create a crash block plugin, which accepts a type: boolean "crash" block setting which will cause the Block plugin's ::build() method to trigger a PHP exception. This is for criterium 1.
3. Add the following:
   

     /**
      * @dataProvider providerRenderComponent
      */
     public function testRenderComponent(array $inputs, string $componentUuid, bool $isPreview = FALSE, ?\Exception $expected_exception, string $expected_output): {
       
     }
   

   to \Drupal\Tests\experience_builder\Kernel\Plugin\ExperienceBuilder\ComponentSource\(Block|Js|SingleDirectory)ComponentTest.

   Make it test all 5 scenarios in scope for this issue, plus one successfully rendering one.

User interface changes

None.