Improve plugin tooling and build process

[thelovekesh]

Currently, the plugin includes vendor and build files in the version control, which increases the size of the repository to checkout and somewhat impacts the developer experience.

Additionally, when the plugin is published, it includes several files that add nothing besides bulking up the plugin; therefore, preferable to remove such files beforehand.

Here are several chores that could be considered:

• [x] Remove vendor and build files from version control.
• [x] Migrate NPM and required configs to the root directory from assets.
• [x] Update required packages with official @wordpress/* packages.
• [x] Update plugin release workflow to add vendor and build files before publishing it.
• [x] Remove unused files with pattern composer.*, vendor/*/*/.editorconfig, vendor/*/*/phpunit. etc. from vendor files as they are not required in production release.
• [ ] Automate tasks like generating readme.txt from README.md instead of maintaining two different filed in VCS.
• [x] Automate the task of drafting the release using GitHub Action for better changelog coverage.

[aviral-mittal]

@hbhalodia Can you please provide a time estimation for this?

[hbhalodia]

Hi @aviral-mittal, I need to go through the process that lovekesh mentioned. I do not have any prior experience with automation. So it can need some time to review, learn and apply the same. I would connect with lovekesh for this findings and would give a proper estimation after that. Thanks.

[hbhalodia]

Hi @thelovekesh, Let me know can when we connect to discuss above workflow. Need to discuss in detail. Thanks.