Add goimports and gofmt check to the static analysis

Gofmt and Goimports should be run on each new PR in order to ensure
there is no future drift from basic go formatting directives. These
checks will simply fail if the code is not correctly formatted.

Author: killianmuldoon

.github/workflows/static-analysis.yaml

@@ -23,6 +23,15 @@ jobs:
     - uses: brpaz/hadolint-action@v1.2.1
       with:
         dockerfile: deploy/images/Dockerfile
+  gofmt-imports:
+    runs-on: ubuntu-latest
+    name: Go Fmt and Go Import
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-go@v2
+        with:
+          go-version: 1.15
+      - run: go get golang.org/x/tools/cmd/goimports; test -z $(goimports -l .) && test -z $(gofmt -l .)
   golangci:
     strategy:
       matrix:

cmd/main.go

@@ -4,6 +4,7 @@ import (
 	"flag"
 	"log"
 	"os"
+
 	"os/signal"
 	"syscall"
 	"time"
@@ -12,6 +13,7 @@ import (
 	"github.com/intel/telemetry-aware-scheduling/pkg/metrics"
 	"github.com/intel/telemetry-aware-scheduling/pkg/scheduler"
 	strategy "github.com/intel/telemetry-aware-scheduling/pkg/strategies/core"
+
 	"github.com/intel/telemetry-aware-scheduling/pkg/strategies/deschedule"
 	"github.com/intel/telemetry-aware-scheduling/pkg/strategies/dontschedule"
 	"github.com/intel/telemetry-aware-scheduling/pkg/strategies/scheduleonmetric"