Use standardized name for build and test tasks

This is the naming convention established in the standardized template project assets.

Author: per1234

.github/workflows/test-go-integration-task.yml

@@ -57,4 +57,4 @@ jobs:
         run: pip install poetry
 
       - name: Run integration tests
-        run: task test-integration
+        run: task go:test-integration

.github/workflows/test-go-task.yml

@@ -48,7 +48,7 @@ jobs:
           version: 3.x
 
       - name: Run unit tests
-        run: task go:test-unit
+        run: task go:test
 
       - name: Send unit tests coverage to Codecov
         if: matrix.operating-system == 'ubuntu-latest'

Taskfile.yml

@@ -41,14 +41,20 @@ vars:
 tasks:
   build:
     desc: Build the project
-    cmds:
-      - go build -v {{.LDFLAGS}}
+    deps:
+      - task: go:build
 
   test:
     desc: Run tests
     cmds:
-      - task: go:test-unit
-      - task: test-integration
+      - task: go:test
+      - task: go:test-integration
+
+  # Source: https://github.com/arduino/tooling-project-assets/blob/main/workflow-templates/assets/go-task/Taskfile.yml
+  go:build:
+    desc: Build the Go code
+    cmds:
+      - go build -v {{.LDFLAGS}}
 
   go:generate:
     desc: Generate Go code
@@ -60,12 +66,12 @@ tasks:
       - go generate ./...
       - task: go:format
 
-  go:test-unit:
+  go:test:
     desc: Run unit tests
     cmds:
       - go test -short -run '{{default ".*" .TEST_REGEX}}' {{default "-v" .GOFLAGS}} -coverprofile=coverage_unit.txt {{default .DEFAULT_GO_PACKAGES .GO_PACKAGES}}
 
-  test-integration:
+  go:test-integration:
     desc: Run integration tests
     cmds:
       - task: build

docs/CONTRIBUTING.md

@@ -118,26 +118,26 @@ task test
 To run only the Go unit tests, run:
 
 ```
-task go:test-unit
+task go:test
 ```
 
 By default, all tests for all Arduino Lint's Go packages are run. To run unit tests for only one or more specific
 packages, you can set the `TARGETS` environment variable, e.g.:
 
 ```
-TARGETS=./internal/rule task go:test-unit
+TARGETS=./internal/rule task go:test
 ```
 
 Alternatively, to run only some specific test(s), you can specify a regex to match against the test function name, e.g.:
 
 ```
-TEST_REGEX='^TestLibraryProperties.*' task go:test-unit
+TEST_REGEX='^TestLibraryProperties.*' task go:test
 ```
 
 Both can be combined as well, typically to run only a specific test:
 
 ```
-TEST_REGEX='^TestFindProjects$' TARGETS=./internal/project task go:test-unit
+TEST_REGEX='^TestFindProjects$' TARGETS=./internal/project task go:test
 ```
 
 #### Integration tests
@@ -153,7 +153,7 @@ For these reasons, in addition to regular unit tests the project has a suite of
 After the software requirements have been installed, you should be able to run the tests with:
 
 ```
-task test-integration
+task go:test-integration
 ```
 
 This will automatically install the necessary dependencies, if not already installed, and run the integration tests