Auto-publish: ForceConfigControl.lightning-flow-scanner-vsx

[RubenHalman]

• I have read the note above about PRs contributing or fixing extensions
• I have tried reaching out to the extension maintainers about publishing this extension to Open VSX (if not, please create an issue in the extension's repo using this template).
• This extension has an OSI-approved OSS license.

Description

Request: Add to auto-publish list for mirroring from VS Code Marketplace:

This change configures the workflow to automatically publish the lightning-flow-scanner-vsx extension to the Open VSX Marketplace. The goal is to reduce maintenance overhead.
The JSON validates against extensions-schema.json, and no other files were modified.
I am also registered author of ForceConfigControl.lightning-flow-scanner-vsx.

• Extension: Lightning Flow Scanner VSX
• Marketplace: marketplace.visualstudio.com/items?itemName=ForceConfigControl.lightning-flow-scanner-vsx
• Repository: github.com/Flow-Scanner/lightning-flow-scanner-vsx

[filiptronicek]

Hey there @Shadow1363 👋
While I appreciate the desire to reduce burden on the extension repo, as per our contributing guidelines:

A goal of Open VSX is to have extension maintainers publish their extensions according to the documentation. The first step we recommend is to open an issue with the extension owner. If the extension owner is unresponsive for some time, this repo (publish-extensions) can be used as a temporary workaround to ensure the extension is published to Open VSX.

The above also includes owners, who should publish the extension from their respective repositories instead of using this one, so that they own the publishing process from end to end and reduce the maintenance burden on our repository, which already has hundreds of extensions which we try to actively reduce.

We also have a guide on doing this via GitHub actions, which you may find useful: https://github.com/EclipseFdn/publish-extensions/blob/master/docs/direct_publish_setup.md.

Let me know if you have any questions!

[Shadow1363]

@filiptronicek pinged the wrong person (again) lol