Fix the issues reported by phpcs

Hi himanshu_jhaloya

I applied your MR !1 in my local with Drupal 9.5.8 to the "Export content xml writer" against version 1.0.x-dev, and PHPCS flagged the issue below

FILE: /Users/studenttrainees/Projects/drupalorgissues/docroot/modules/contrib/export_content_xml_writer/export_content_xml_writer.info.yml
------------------------------------------------------------------------------------------------------------------------------------------
FOUND 0 ERRORS AND 3 WARNINGS AFFECTING 1 LINE
------------------------------------------------------------------------------------------------------------------------------------------
1 | WARNING | Remove "project" from the info file, it will be added by drupal.org packaging automatically
1 | WARNING | Remove "datestamp" from the info file, it will be added by drupal.org packaging automatically
1 | WARNING | Remove "version" from the info file, it will be added by drupal.org packaging automatically
------------------------------------------------------------------------------------------------------------------------------------------

Time: 182ms; Memory: 10MB

Please look at the screenshot attached for your reference.

Thanks

@clarkssquared add also the PHPCS flagged command.

Hi himanshu_jhaloya

The PHPCS command I used is:
phpcs --standard=Drupal,DrupalPractice --extensions=php,module,inc,install,test,profile,theme,css,info,txt,md,yml export_content_xml_writer

checkout the branch phpcs @clarkssquared

We do not use issue tags that are also the issue title. That is explained in the field description: Do NOT use tags for adding random keywords or duplicating any other fields.

+/**
+ * {@inheritDoc}
+ */

{@inheritDoc} is not used for a class documentation comment.

+  /**
+   * Entity type manager service.
+   *
+   * @var \Drupal\Core\Entity\EntityTypeManagerInterface
+   */
+  protected $entityTypeManager;
+
+  /**
+   * Content of node.
+   *
+   * @var string
+   */
+  protected $content;

The short descriptions are missing an article.

+  /**
+   * Constructs media integration plugin.
+   *
+   * @param array $configuration
+   *   A configuration array containing information about the plugin instance.
+   * @param string $plugin_id

The short description needs to include class name and its namespace, not a description of the created object.

+  /**
+   * {@inheritdoc}
+   */
+  public static function create(ContainerInterface $container, array $configuration, $plugin_id, $plugin_definition) {
+    return new static(
+      $configuration,
+      $plugin_id,
+      $plugin_definition,
+      $container->get('entity_type.manager')
+    );
+  }

A class without parent classes nor implementing interfaces cannot use {@inheritdoc}. That method is useless, if the plugin does not implement a specific interface.
I would rather leave that out for a different issue, since that is a bug, not a matter of following the coding standards, though. A plugin class must at least implement an interface (in the simpler cases). This class does not implement any interface.