Add a library item summary formatter

Lets add some test for this.

1. +++ b/modules/paragraphs_library/src/Plugin/Field/FieldFormatter/LibraryItemSummaryFormatter.php
   @@ -0,0 +1,79 @@
   +        if (!$items->getEntity()->isPublished()) {
   +          $published = [
   +            '#theme' => 'paragraphs_info_icon',
   +            '#message' => $this->t('Unpublished'),
   +            '#icon' => 'view',
   +          ];
   +          $elements[$delta]['info'] += $published;
   +        }
   +      }
   

   I think we can re-use the existing class here for most things. a diff between the two files shows it is identical except that extra icon that we're adding.

   So try to do an extends ParagraphsSummaryFormatter here and then call parent::build() and then you only need to add this extra visibility icon. IMHO you could even skip the foreach loop, as we know that this is for the library item base field which has cardinality 1 and so only has delta 0.

2. +++ b/modules/paragraphs_library/src/Plugin/Field/FieldFormatter/LibraryItemSummaryFormatter.php
   @@ -0,0 +1,79 @@
   +  /**
   +   * {@inheritdoc}
   +   */
   +  public static function isApplicable(FieldDefinitionInterface $field_definition) {
   +    $target_type = $field_definition->getSetting('target_type');
   +    $paragraph_type = \Drupal::entityTypeManager()->getDefinition($target_type);
   +    if ($paragraph_type) {
   +      return $paragraph_type->isSubclassOf(ParagraphInterface::class);
   +    }
   +    return FALSE;
   +  }
   +
   

   isSubclassOf is deprecated, looks like this was copied from an older version of the other summary class.

   I first thought we can just drop this with the changed parent, but actually, that would make this formatter show up on all paragraph fields, we don't want that. WE only want it on the paragraph field on library items. So instead of this, check getTargetEntityTypeId() of $field_definition and the field name to only allow this being used on this specific field.

Needs a reroll as another issue added test logic in the same place.

Rerolled.

Not sure if something has changed in Paragraphs default configuration since #8 to result in test #10 fails...

Fixed and improved tests.

Hm, possibly the behavior change is the published-by-default change that the other issue did that this conflicted with? Test looks good to me, committed.