Update metadata for Lightning-Flow-Scanner

[RubenHalman]

@nvuillam @echoix

As discussed in the related issue, all versions below v5 have been unpublished, namespace remains unchanged I noticed that MegaLinter already lists 5.6.2 as the current version, but when testing megalinter, it doesn’t appear to include LFS yet.

This PR adds the latest version and documentation on LFS to ensure it’s available in the latest release.

---

Note

Points Lightning Flow Scanner metadata to the new CLI repository/org, updates banner image, and switches VS Code marketplace link.

• Salesforce descriptor (megalinter/descriptors/salesforce.megalinter-descriptor.yml):
  • Lightning Flow Scanner:
    • Update linter_url and linter_repo to Flow-Scanner/lightning-flow-scanner-cli.
    • Update linter_banner_image_url to new CLI repo image path.
    • Update VS Code extension URL to ForceConfigControl.lightning-flow-scanner-vsx.

^{Written by Cursor Bugbot for commit ee59c96. This will update automatically on new commits. Configure here.}

[RubenHalman]

@nvuillam @echoix Hello, I believe this passes the tests(it is mostly just documentation updates) and allows lightning flow scanner to be re-enabled in Megalinter after unpublishing as explained in the v5 core fix. Thank you for your consideration.

[RubenHalman]

Dear @nvuillam and @echoix , I fully understand if LFS will not be re-enabled. However, can we still merge the changes to the documentation so that the information on Megalinter remains accurate?

[echoix]

Please, could you update the contents you want updated in the .megalinter-descriptor.yaml file? The docs are generated from there, so the Md file changes would be lost

[RubenHalman]

@echoix done, thank you!

[echoix]

With this state, I'm comfortable in having better metadata. For follow ups, it'll need feedback from @nvuillam. It'll need to respect one of our principles that it must be generally accepted and used by the community of that tool. (I can't really judge for Salesforce).

I adjusted the PR title.

[RubenHalman]

@echoix really appreciated. I am excited for the opportunity to contribute to Megalinter, even if it is just fixing broken links!