Fix bugs in WordPress 5.8 related to withColors and modernize code in blocks

[acketon]

• Bug fix: Intro Paragraph block's onSplit function wasn't working to add a paragraph block when the user hits enter.
• Bug Fix: Intro Paragraph block was retaining the dropcap when switching Block Styles. Had to change how className was used since the old approach from the beta version of Gutenberg conflicts with current attribute and property usage of className.
• Multiple blocks were using the "full" image size in the Background component. This has been changed now to the large size instead. This should be a safe change for most blocks but may result in some layout bugs. Loading the full size however is not acceptable as the files sizes can be extreme.
• Block Color Palette Options WP 5.8 bug fixes:
  • Stats color options fixed
    • Fix 5.8 color palette issues in withColors(), add Example for inserter, remove 4.9 fallback code
  • Modal color options fixed
    • Fix 5.8 color palette issues in withColors(), add Example for inserter, remove 4.9 fallback code
  • Leadin color options fixed
    • Fix 5.8 color palette issues in withColors(), add Example for inserter, remove 4.9 fallback code
  • Drawer color options fixed
    • Fix 5.8 color palette issues in withColors(), add Example for inserter, remove 4.9 fallback code
  • Intro Paragraph color options fixed
    • Fix 5.8 color palette issues in withColors(), add Example for inserter, remove 4.9 fallback code
  • Button block color options fixed
    • Fix 5.8 color palette issues in withColors(), add Example for inserter, remove 4.9 fallback code
  • Pullquote block color options fixed
    • Fix 5.8 color palette issues in withColors(), add Example for inserter, remove 4.9 fallback code
  • Aside Block color options fixed
    • Fix 5.8 color palette issues in withColors(), add Example for inserter, remove 4.9 fallback code

[timkingbu]

const getColorSlug = ( color ) => { ... }; is repeated at least 7 times, let's pull this out into a common library.

[acketon]

yeah, I was contemplating this. I think I can add it to the ThemeOptions component but I'll have to modernize that component file too. I can make that change to the PR.

[timkingbu]

Maybe becomes an imported component?

[timkingbu]

Everything looks good. I was able to run npm run build with no errors (but lots of warnings). A quick check of the editor and frontend - everything appears to be working.

I did not do any VRTs against the current version of BU Blocks.

Other things to note:

• npm audit produces 19 vulnerabilities (6 low, 3 moderate, 10 high)
• npm run lint:js produces 229 problems (226 errors, 3 warnings)