[FEATURE]: add CI e2e setup to plugins

[shahrokni]

Relates to perses/perses#3799

E2E setup

This change adds e2e set up into the plugin repo. Using the PERSES_PLUGIN_ARCHIVE_PATHS parameter we are able to inject the built plugins (archive files) into the running instance of Perses. For more information please take a look at https://perses.dev/perses/docs/configuration/configuration/

⚠️ Use a recent tag. The mentioned config is pretty new! I used the following tag,

main-2026-02-26-739dc289-distroless-debug

Check: https://hub.docker.com/r/persesdev/perses

How to test this

• Edit a plugin
• For example you can change its name from rsbuild.config
• And just push
• You can check the plugins endpoint and see that the substitute archive is in place
• You can use the following code to assure your change is also available from the tests

/* WAS ONLY ADDED FOR DEMONSTRATIONS*/
test.describe('table Plugin', () => {
  test('ONLY FOR PR DEMONSTRATION', async ({ request }) => {
    const res = await request.get('http://localhost:8080/api/v1/plugins');
    expect(res.ok()).toBeTruthy();
    const plugins = await res.json();
    console.log('--- Current Perses Plugins ---');
    console.log(
      JSON.stringify(
        Array.from(plugins).map((p) => p.spec),
        null,
        2
      )
    );
  });
});

http://localhost:8080/api/v1/plugins

Provisioning

Provisioning was also set up to ease the testing process. The content doesn't matter at this point. The aim was only to make sure it is ready for the further steps.

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

[Nexucis]

@jgbernalp over to you, just to ensure you are fine with this approach.

@shahrokni can you solve the conflicts please ?

[shahrokni]

@jgbernalp over to you, just to ensure you are fine with this approach.

@shahrokni can you solve the conflicts please ?

Yes sure, I will rebase main and resolve the conflicts

[Nexucis]

Hopefully this file should not be necessary as e2e is part of the workspace

[Nexucis]

excepting my last comment, looks good to me. Well done @shahrokni !