Add 2024 files

[jasondaming]

No description provided.

[PeterJohnson]

Why is Phoenix6 using "frcjson"?

[jasondaming]

I think the answer should come from @JCaporuscio but my understanding is that because we want a different json file for each version that his is how those are automatically generated. I don't think that has to be the case for the future but it may be? The only real requirement that we have is that the name cannot clash per year with another "vendor".

Keep in mind that this is not the actual name that the user sees. That is specified in the file (fileName key) in this case "Phoenix6.json"

[JCaporuscio]

That file naming is how our vendordeps are internally generated and archived, so to grab multiple specific versions all at once it's (currently) the only option.

In the case where we add each json version as we go (say, a PR each time we release) the naming would match the current public-facing naming (ie Phoenix6-[version].json).

For an initial batch add like this, since there's only half a dozen files or so I would highly recommend renaming them to match the public-facing naming to avoid future confusion. So "Phoenix6-[version].json" or "Phoenix5-[version]".json depending on which lib it is.