Add unit tests and CI

[jw3]

The unit tests and workflow configuration were removed in jw3/example-daffodil-vscode@92d5c7d to simplify licensing for the move.

These need added back, while this time using schema and test data that are license compatible with this repo.

[stevedlawrence]

When this is added, I suggest you base it off of the Daffodil file. Specifically, ignoring dependabot branches, test matrices (if needed), Apahce Rat check, Single commit PR, etc.

[shanedell]

@stevedlawrence I was working on this one and was trying to follow the apache/daffodil/.github/workflows/main.yml for how to setup the CI.

However when it comes to the Apache Rat Check, would we want to get that setup as separate PR? I think I could easily get that stuff added in but I wanted to see how thought best to approach this? I did notice the comment on #26 about this so wanted to make sure to verify best solution.

Do you want the CI for this project to be the same as apache/daffodil where it is doing multiple things in the one CI? As I was just going to make a .github/workflows/tests.yml for running the unit tests and more or so making all CI items being its own separate thing, but again want to make sure I do what is proper in this case.

[stevedlawrence]

I'm fine with Rat being a separate PR.

In Daffodil we did have a couple separate yml files, but we eventually combined into a single file. We found it reduced duplication and made it a bit easier to manage and visually everything that is checked in a PR. So I'd lean towards that. But this is a different project so if that doesn't make sense I'm open to alternatives. But the more similar things are, the easier it is for people to switch become familiar with both projects.

[shanedell]

That makes sense, do you think it would be best for us to keep them separate for the time being then once we have the pieces we want in the CI we can merge them together?

[stevedlawrence]

I have no strong preference. It'll probably be easier to make suggestions once we see the actual checks (it's not totally clear to me what is involved with CI for this vscode project). So I suggest do what you feel is right, and once we have something concrete to look at we can determine if there's a better way to organize things.