feat(ci): consolidate linter implementations to use reviewdog for better Github integration

[Neudrino]

Summary

• add tflint to reviewdog to have this integrated with Github as well.

Test Plan

• CI
  • no change to Terraform files: https://github.com/magma/magma/actions/runs/2219664144
  • change to Terraform files which are green: https://github.com/magma/magma/actions/runs/2219674103

Additional information

• requires ci: reviewdog filter consolidation #12293

[github-actions]

Thanks for opening a PR! 💯

A couple initial guidelines

• All commits must be signed off. This is enforced by DCO check.
• All PR titles must follow the semantic commits format. This is enforced by Semantic PR.

Howto

• Reviews. The "Reviewers" listed for this PR are the Magma maintainers who will shepherd it.
• Checks. All required CI checks must pass before merge.
• Merge. Once approved and passing CI checks, use the ready2merge label to indicate the maintainers can merge your PR.

More info

Please take a moment to read through the Magma project's

• Contributing Conventions for norms around contributed code

If this is your first Magma PR, also consider reading

• Developer Onboarding for onboarding as a new Magma developer
• Development Workflow for guidance on your first pull request
• CI Checks for points of contact for failing or flaky CI checks
• GitHub-to-Slack mappings for Magma maintainers for guidance on how to contact maintainers on Slack

[github-actions]

cloud-workflow

0 files  0 suites   0s ⏱️
0 tests 0 ✔️ 0 💤 0 ❌

Results for commit 26a79a9.

[maxhbr]

Changes look good, but PR title does not follow semantic commits format.

[maxhbr]

Ah, ci: is allowed, but I would prefer to have feat(ci): or fix(ci):.

I think ci should be used in the context of for example ci(orc8r): if you do ci work for orc8r. If a feature is added to ci it should be feat(ci).

[maxhbr]

LGTM