feat: add vegaos platform compatibility

[moskalakamil]

📝 Why & how

Hey folks 👋

I added support for the Vega OS platform and wanted to leave this PR open for some discussion.

So far, the directory only had “Works with Fire OS,” but since Fire TV devices are moving over to Vega, I figured it might make sense to bring it up here.

Should we keep Vega as a separate platform? Replace Fire OS? Or maybe have both available through filtering?

---

To mark Vega OS support in a library entry, just add:

{
  "githubUrl": "https://github.com/user/library",
  "vegaos": true
}

This is just a trial addition - curious to hear what do you think!

✅ Checklist

• Added library to react-native-libraries.json
• Updated library in react-native-libraries.json

• Documented in this PR how to use the feature or replicate the bug.
• Documented in this PR how you fixed an issue or created the feature.

[Simek]

Hey @moskalakamil, thanks for working on those changes! 👍 I was think about this a bit for a while, and after digging more few days ago into how Vega OS works currently, I'm not sure if it is not too early to add it to the directory. I wonder what others would think tho.

The problems I see at this time:

• it's not the out-of-tree platform in the sense like others are, there is no fork/package to install and add to your project, you need to relay fully on the provided templates or VS Code extension, and it seems that the app code and dependencies cannot be easily shared with other other platforms, within the same project
• all mentioned compatible packages are modified forks, which are published under different npm names (see npm registry), scoped within @amazon-devices, which currently makes an impression that regular packages cannot be compatible with Vega OS if they support other platforms (hope this will change in the future, or it is just a wrong impression)
• adding Vega compatibility would require us to add to the list all of the existing forks seen in the link above, since otherwise we would not have any packages listed as compatible, but this would pollute directory a bit, and and can cause confusion for the user when searching by package name, especially mentioning the fact that no all package metadata is altered in published forks, in few cases README, repository links, website and other data points to the origin repository or docs which do not have any affiliation with, or information about Vega OS (and those metadata are the core source of information for the directory and our APIs)
• package name used on few documentation pages (react-native-vega) is not owned by Amazon, which could lead to some confusion, some clarification and docs updates on Amazon side might be needed to address this

So if we decide to move on this addition, at this time I would prefer add this as a compatibility flag (just like Expo Go or Fire OS), and not as a separate platform (at least for now). Could you revert the footer change, and refactor the flag to be a compatibility one? This way it should be easier to move the contribution forward.

Maybe some Amazon folks (previously responsible for adding Fire OS flag) can chime in, and provide a bit more context on their vision, and the plans for the future, CC @mosesroth, @chris-trag

[moskalakamil]

Totally agree! I actually thought about opening this as a discussion first, but since it was just a quick one-prompt change, I figured I’d throw it in as a PR instead.
Let’s wait a bit to hear from the Amazon folks - once we get their input, I’ll adjust things accordingly :D

[chris-trag]

Hey @Simek & @moskalakamil - thx so much for the discussion and points here.

I agree with Simon that Vega OS & the SDK have several milestones we have to reach during this Open Beta period before we can determine if we're at the out of tree platform level versus a device-specific flag.

I'm conscious that we need to earn trust and work through which "ported" libraries should get upstreamed back to the main projects versus living in their current namespaces while we work through compatibility feedback & tv specific feature requests.

For now, I love the idea of a compatibility flag for works with Fire OS and I can commit to having myself and our team testing & verifying functionality ongoing each time a library is added.

In addition, we're keeping this community post up to date each time we have a new library with support: https://community.amazondeveloper.com/t/vega-supported-libraries-and-services/1552

@moskalakamil let me know if you need any help with the change @Simek recommended for this PR.

[moskalakamil]

Hey @Simek, I updated the flag

[Simek]

Thanks for the updates @moskalakamil! 👍

After thinking a bit more about this, we can improve the clarity and avoid the repetition of libraries, if we allow vegaOs field to accept strings which would point out to the alternate Vega OS packages in npm registry, and then link up visual tag on the library tile with that.

The follow up would be to port over the data from mentioned by Chris list to the react-native-libraries.json. Let me know if you are interested on working on those two change, if not we can merge it as-is (with unrelated changes revert), and I can continue the efforts in a follow-up PR.

[Simek]

Let's revert the README.md changes not related to Vega OS addition.

[Simek]

Let's revert schema changes not related to Vega OS.