feat: allowing extension to provide routeId to progress task

[axel7083]

What does this PR do?

Allow extensions to provide a navigation object when using window.withProgress.

Screenshot / video of UI

extension-custom-rout.mp4

What issues does this PR fix or reference?

Fixes #7709

How to test this PR?

• Tests are covering the bug fix or the new feature

Testing manually

Inside the activate of an extension add the following

  extensionApi.commands.registerCommand('podman.dummy-command-id', (...args) => {
    console.log('[podman] command triggered ', args);
    return extensionApi.navigation.navigateToContainers();
  });

  extensionApi.navigation.register('dummy-route-id', 'podman.dummy-command-id');

  extensionApi.window.withProgress<string>({
    location: ProgressLocation.TASK_WIDGET,
    details: {
      routeId: 'dummy-route-id',
      routeArfs: ['tracking-id'],
    },
    title: 'Task example'
  }, async (): Promise<string> => {
    return new Promise<string>((resolve, reject) => {
      setTimeout(() => {
        resolve('patate');
      }, 10 * 1000);
    });
  }).catch((err: unknown) => {
    console.error(err);
  });

and add the following to the extension package.json

{
....
  "contributes": {
    "commands": [
      {
        "command": "podman.dummy-command-id",
        "title": "Podman: Dummy command (navigation related)"
      },
....

1. Then activate / deactivate the given extension
2. See the TaskManager

[gastoner]

LGTM, Works nicely!

[benoitf]

I still believe View details or Inspect is more accurate but as it's not part of the spec (.d.ts file), it can be easily changed over time (or not) later.

can merge and discuss it during UX discussions