Bugfix/Stringify Task ENUMs for Presentation and PanelKind

[kenneth-marut-work]

What it does

This PR addresses #7956 where ENUM values for PanelKind and RevealKind were not properly being stringified to their values defined in the task-schema-updated.ts (referenced below) when using .setTaskConfigurations() to write tasks to a tasks.json file, causing an Invalid task configurations are found error :

theia/packages/task/src/browser/task-schema-updater.ts

Line 572 in 309b218

enum: ['always', 'silent', 'never'],

theia/packages/task/src/browser/task-schema-updater.ts

Line 583 in 309b218

enum: ['shared', 'dedicated', 'new'],

How to test

• Create an extension that injects the TaskConfigurationManager
• Build an object of type TaskConfiguration with some values (fill in proper scope/source value), use
  enum types for presentation panel and reveal, for example:

       const pendingTaskConfiguration: TaskConfiguration = {
            label: 'my task',
            type: 'shell',
            command: 'top',
            problemMatcher: [],
            args: '',
            _scope: 2,
            _source: scopeURI,
            options: {
                cwd: '',
            },
            presentation: {
                reveal: RevealKind.Always,
                panel: PanelKind.Shared
            },
        };

• Attempt to call this.taskConfigurationManager.setTaskConfigurations(scopeURI, [pendingTaskConfiguration])

• Open corresponding tasks.json file and observe that reveal and panel values have been properly set to their string values and no errors are thrown.

Review checklist

• as an author, I have thoroughly tested my changes and carefully followed the review guidelines

Reminder for reviewers

• as a reviewer, I agree to behave in accordance with the review guidelines

[marcdumais-work]

@elaihau do you have time to review this PR?

[elaihau]

I tested this change in my local environment. It worked properly. Thank you for the work !

[marcdumais-work]

@akosyakov fine to merge?

[RomanNikitenko]

I see that the corresponding API objects use different values. VS Code has other values as well.
So we should test some Theia plugin or VS Code extension which uses these objects to avoid regression from plugin side.

I can check this use case today, sorry for the delay...

[RomanNikitenko]

I tried to test the use case described above, but faced with the related issue for master branch #8047

So, it's OK for me to merge the PR as is, we can come back and check the use case after resolving #8047

[marcdumais-work]

@elaihau Ready to merge I think?

[elaihau]

@elaihau Ready to merge I think?

@marcdumais-work Yes. I don't see objections from Roman either.

[marcdumais-work]

Yes. I don't see objections from Roman either.

Please do the honours, Liang

[elaihau]

Please do the honours, Liang

Oui chef

[marcdumais-work]

Oui chef

👍

[kenneth-marut-work]

thanks for the review + merge ✌