Isolate actions strategies in order to code improvement and programmatic usage.

[obetomuniz]

What kind of change does this PR introduce? (check at least one)

• Bugfix
• Feature
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change? (check one)

• Yes
• No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

• It's submitted to the dev branch for v2.x (or to a previous version branch), not the master branch
• When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
• New/updated tests are included

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

This is a proposal to modernize the library in order to support more features, scale the current features in a healthy way and give more flexibility to the user.

[helderberto]

IMHO, nothing is blocking, great work! 🚀

[ktfth]

Good work

[vitormalencar]

Nice work @obetomuniz, I just have one small question, does our TS type definitions need to be updated as well?

[obetomuniz]

Nice work @obetomuniz, I just have one small question, does our TS type definitions need to be updated as well?

That's definitely a thing to consider since we now have two new static methods being exposed. I will take a look on it today before merge. Tks man!

[vitormalencar]

Nice 👏

[howlger]

In clipboard.min.js o.remove() (instead of o.parentNode.removeChild(o)) seems wrong to me, since Internet Explorer 11 does not support remove() (causing SCRIPT438: Object doesn't support property or method 'remove' error/exception).