Code Standards Cleanup

The issue summary should always describe what the issue is trying to fix and, in the case of coding standards issues, show which command and arguments have been used and which report that command shown. In this way, project maintainers can verify the patch/MR fixes all the warnings/errors.

Also, since the module has Drupal 8 releases, should not this fixed for the Drupal 8 branch, first?

Thank you all for your work on this, unfortunately the work here is outdated and has been handled is separate issues elsewhere including:

• 📌 Fix ESLint Errors following Drupal coding standards and best practices Active
• 🐛 Coding standards and best practices Active

If you have time, we could use your review the following issues if still open when you read this.

1. 📌 Delete unused color.js file and remove from library definitions. Active
2. 📌 Fix stylelint issues. Active