[FEATURE]: add CI e2e setup to plugins

[shahrokni]

Relates to perses/perses#3799

CI e2e Setup

This change adds Playwright e2e testing setup to the Plugins repo.
It tests all plugins which have a test directory under e2e/tests.

Demonstration of tests results for the table and trace table plugins

The idea

Simply speaking the idea is to use the latest version of Perses and CLI to run tests over individual plugins.

• Get persesdev/perses:desired_version
• Download and install the latest version of Perses CLI and run it on the VM
• Install Browsers
• Loop > Pick plugins from the array of plugins ♻️
• Attach to the plugin using CLI plugin start command
• Capture the test results for the plugin
• Continue the Loop > the next plugin ♻️

Why should we install Perses CLI binary ❓

Couldn't we use the CLI in the running container? Apparently, not. Perses image is distroless meaning, npm/node are not included. Under the hood Plugin Start command uses node.

In software development and DevOps, a distroless image is a minimal container image that contains only your application and its runtime dependencies.

Therefore, we should run the binary CLI on the VM and communicate with the running Perses.

Screenshots

Checklist

• Pull request has a descriptive title and context useful to a reviewer.
• Pull request title follows the [<catalog_entry>] <commit message> naming convention using one of the
  following catalog_entry values: FEATURE, ENHANCEMENT, BUGFIX, BREAKINGCHANGE, DOC,IGNORE.
• All commits have DCO signoffs.

UI Changes

• Changes that impact the UI include screenshots and/or screencasts of the relevant changes.
• Code follows the UI guidelines.

[Nexucis]

overall, thank you for putting this in place.

I have added few suggestions that will improve the CI/CD and simplify it.

I will probably add more comments later, but this is already a good step