Remove noncompulsory plugin headers

[pierlon]

Summary

Since we're not bundling our own translations, I think we can remove the "Domain Path" header. And as stated in the WP handbook:

The Domain Path header can be omitted if the plugin is in the official WordPress Plugin Directory.

Also it seems we can remove the "Text Domain" header. As stated by the handbook:

Since WordPress 4.6 the Text Domain header is optional because it must be the same as the plugin slug. There is no harm in including it, but it is not required.

This is confirmed by the following condition in Core:

        // If no text domain is defined fall back to the plugin slug.
	if ( ! $plugin_data['TextDomain'] ) {
		$plugin_slug = dirname( plugin_basename( $plugin_file ) );
		if ( '.' !== $plugin_slug && false === strpos( $plugin_slug, '/' ) ) {
			$plugin_data['TextDomain'] = $plugin_slug;
		}
	}

Checklist

• My pull request is addressing an open issue (please create one otherwise).
• My code is tested and passes existing tests.
• My code follows the Engineering Guidelines (updates are often made to the guidelines, check it out periodically).

[pierlon]

I'm also wondering if there would be any harm in removing the Text Domain header. As stated by the handbook:

Since WordPress 4.6 the Text Domain header is optional because it must be the same as the plugin slug. There is no harm in including it, but it is not required.

[github-actions]

Plugin builds for 82eb5d0 are ready 🛎️!

• Download development build
• Download production build

[westonruter]

I'm also wondering if there would be any harm in removing the Text Domain header.

Sure, let's remove it.

[westonruter]

Rebasing onto develop to fix build.