Prepare for release

[evoactivity]

• Add VSCODE_STORE_TOKEN secret
• Add OPEN_VSX_STORE_TOKEN secret
• Update package.json package.json changes #43
• Make workflow manually runnable

[lifeart]

@evoactivity in addition, we need to check locally if any issues appears if user has both official & unstable els installed and enabled. And if some - we need to land proper changes to any to avoid conflicts

[evoactivity]

We could detect in uELS if ELS is installed and bail out, printing a message to the output that ELS should be disabled to use uELS. What do you think?

[lifeart]

@evoactivity yep, we should be able to get list of enabled extensions

[evoactivity]

Extension has been un-deprecated. I'm aiming to get things release this week.

[evoactivity]

The release to the vscode marketplace worked
https://marketplace.visualstudio.com/items?itemName=EmberTooling.vscode-ember

Open VSX is being a silly little goose, so I've contacted them to fix the account.

❌  Your Publisher Agreement with the Eclipse Foundation is outdated (version 1.0). The current version is 1.

[evoactivity]

https://open-vsx.org/extension/embertooling/vscode-ember

open vsx fixed their issue and release now working 🎉