Provide licensing information according to REUSE Specification version 3.3 for generated editor SDK files

[kalrish]

What's the problem this PR addresses?

The REUSE Specification requires licensing information for each and every file in a repository; as their FAQ states, "you cannot exclude files from REUSE compliance testing". Files generated by the editor SDK tool in the directory .yarn/sdks are meant to be committed, but they lack the licensing information required by the REUSE Specification. To adhere to the REUSE Specification, repositories that include Yarn editor SDKs must therefore associate licensing information with the editor SDK files with a separately maintained REUSE.toml file, as I've done for my blog.

How did you fix it?

I made the editor SDK tool:

• include licensing information in JavaScript files it generates; and
• generate a REUSE.toml file that associates licensing information with the file package.json that every editor SDK has.

I based the licensing information on the file LICENSE.md.

Checklist

• I have read the Contributing Guide.

• I have set the packages that need to be released for my changes to be effective.

• I will check that all automated PR checks pass before the PR gets reviewed.

[arcanis]

I don't know this REUSE spec, and I'm not very comfortable adding to a core library dependencies to a third-party file parser we don't use elsewhere just for the sake of it.

[kalrish]

Thank you for reviewing my proposal so quickly :).

I don't know this REUSE spec, and I'm not very comfortable adding to a core library dependencies to a third-party file parser we don't use elsewhere just for the sake of it.

I specifically chose @iarna/toml because it is listed as a dependency of the root package, although it doesn't seem to be used anywhere, as you say.

Do you want me to:

• search for a more reputable and currently maintained TOML parser,
• rework the code to generate REUSE.toml files from a simple string template without any parser or
• withdraw the pull request altogether?