Use relevant metadata file when determining framework dependency versions

These workflows support multiple projects in subfolders of the repository. The version of the frameworks (Go and
Node.js) to use is determined from the content of the metadata files. Previously the workflow always used the file
located in the root of the repository. The versioning data in that file won't necessarily be correct for the projects in
subfolders, so the metadata for the individual project should be used instead.

Author: per1234

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

@@ -110,7 +110,7 @@ jobs:
       - name: Install Go
         uses: actions/setup-go@v6
         with:
-          go-version-file: go.mod
+          go-version-file: ${{ matrix.module.path }}/go.mod
 
       - name: Install Task
         uses: arduino/setup-task@v2
@@ -153,7 +153,7 @@ jobs:
       - name: Install Go
         uses: actions/setup-go@v6
         with:
-          go-version-file: go.mod
+          go-version-file: ${{ matrix.module.path }}/go.mod
 
       - name: Install Task
         uses: arduino/setup-task@v2
@@ -196,7 +196,7 @@ jobs:
       - name: Install Go
         uses: actions/setup-go@v6
         with:
-          go-version-file: go.mod
+          go-version-file: ${{ matrix.module.path }}/go.mod
 
       - name: Install Task
         uses: arduino/setup-task@v2
@@ -239,7 +239,7 @@ jobs:
       - name: Install Go
         uses: actions/setup-go@v6
         with:
-          go-version-file: go.mod
+          go-version-file: ${{ matrix.module.path }}/go.mod
 
       - name: Install Task
         uses: arduino/setup-task@v2

.github/workflows/check-npm-task.yml

@@ -107,7 +107,7 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v5
         with:
-          node-version-file: package.json
+          node-version-file: "${{ matrix.project.path }}/package.json"
 
       - name: Install Task
         uses: arduino/setup-task@v2