Set up continuous integration automation

[LarsKemmann]

Goal: Prevent as many defects as possible from getting merged, before even getting to a PR.

• Look around at the .pbip community and identify any appropriate PR validation automation tools that can help with continuous integration. Look at both Microsoft guidance and community recommendations. This can include linters (for naming conventions and validation in VS Code), other error checking tools, possibly AI-based DAX code reviewers. 😁
• Define a list of automation tools to use.
• Implement the VS Code workspace settings to apply those tools to local development in the IDE.
• Implement the GitHub Actions needed to apply those tools to PRs for validation (continuous integration).

[LarsKemmann]

Here are some examples of automated quality checks (community-provided) and how to use them in one example build pipeline (Azure DevOps, rather than GitHub Actions, but the concepts are the same).
https://learn.microsoft.com/en-us/power-bi/developer/projects/projects-build-pipelines

[LarsKemmann]

Goal is to have a set of automated checks that run as a GitHub Action against every pull request. This should not require actual data refreshes, just static code analysis of the .pbip and related files.