fix: deprecated ci action and minor typo

Signed-off-by: Luca Marchiori <luca.marchiori@secomind.com>

Author: lucamarchiori

.github/workflows/go-mod-tidy.yaml

@@ -21,7 +21,7 @@ jobs:
   go-mod-tidy:
     runs-on: ubuntu-22.04
     steps:
-    - uses: actions/checkout@v3
+    - uses: actions/checkout@v4
     - uses: actions/setup-go@v4
       with:
         go-version: v1.20.x

.github/workflows/golangci-lint.yaml

@@ -21,7 +21,7 @@ jobs:
   golangci-lint:
     runs-on: ubuntu-22.04
     steps:
-    - uses: actions/checkout@v3
+    - uses: actions/checkout@v4
     # Since v3, golangci-lint needs explicit go-setup
     - uses: actions/setup-go@v4
       with:

.github/workflows/goreleaser.yml

@@ -11,7 +11,7 @@ jobs:
     runs-on: ubuntu-22.04
     steps:
     - name: Checkout
-      uses: actions/checkout@v3
+      uses: actions/checkout@v4
       with:
         fetch-depth: 0
     - name: Set up Go 1.20

.github/workflows/main.yml

@@ -19,7 +19,7 @@ jobs:
         os: [ubuntu-22.04, macos-latest, windows-latest]
     runs-on: ${{ matrix.os }}
     steps:
-    - uses: actions/checkout@v3
+    - uses: actions/checkout@v4
 
     - name: Set up Go ${{ matrix.go }}
       uses: actions/setup-go@v4

README.md

@@ -72,12 +72,12 @@ Generally speaking, one of those could be written like
 ```
 or, for aggregated interfaces, like a json object:
 ```
- astartectl appengine devices publish-datastream 2TBn-jNESuuHamE2Zo1anA com.my.interface.aggregated /my/path  '{"path1": "value2","path2":"value2"}'
+ astartectl appengine devices publish-datastream 2TBn-jNESuuHamE2Zo1anA com.my.interface.aggregated /my/path  '{"path1": "value1","path2":"value2"}'
 ```
 
 Please note, "value" is whatever your raw value is, no encapsulation whatsoever is required by astarte or astartectl (but you can provide your own, if you need it). 
 Exceptions follow:
 - arrays are written like ["value", "anothervalue"] (depending on your shell, this can also be "['value', 'anothervalue']", please check before using in a production env)
 - aggregates values could be anything accepted by astarte, in case of arrays they follow the above rule
 - binaryblobs must be base64 encoded
-- datetime is based on an external library that is flexible enough to translate a fairly high number of different formats, further documentation and supported formats can be found [here](https://github.com/araddon/dateparse)
+- datetime is based on an external library that is flexible enough to translate a fairly high number of different formats, further documentation and supported formats can be found [here](https://github.com/araddon/dateparse)