refactor: simplify README instructions for local development and testing

Author: Le-Caignec

README.md

@@ -13,7 +13,6 @@ Check how to export handlers with [Matchstick - Test Coverage documentation](htt
 > [!NOTE]
 > Since Matchstick code coverage is in very early stages, Matchstick cannot check for branch coverage, but rely on the assertion that a given handler has been called.
 
-
 ## local dev
 
 run local services:
@@ -34,31 +33,24 @@ npm ci
 generate code
 
 ```sh
-npx graph codegen subgraph.test.yaml
-npx graph build subgraph.test.yaml
+npm run codegen
 ```
 
 deploy the subgraph on local node
 
 ```sh
-# create once
-npx graph create test/poco --node http://127.0.0.1:8020
-npx graph deploy test/poco subgraph.test.yaml --node http://127.0.0.1:8020 --ipfs http://127.0.01:5001 --version-label dev
+npm run start-test-stack
 ```
 
-test/poco subgraph graphql API enpoints:
-
-- queries: <http://127.0.0.1:8000/subgraphs/name/test/poco>
-- subscriptions: <ws://127.0.0.1:8001/subgraphs/name/test/poco>
-
-debugging:
+run integration tests
 
-- monitoring: <http://127.0.0.1:8030/>
-- prometeus: <http://127.0.0.1:8040/>
-- graphnode logs: `docker logs -f test_graphnode_1`
+```sh
+npm run itest
+```
 
-_NB_: other blockchains setups are availables in [docker/README.md](./docker/README.md).
+test/poco subgraph graphql API enpoints:
 
+- queries: <http://127.0.0.1:8000/subgraphs/name/test/poco>
 
 ---
 
@@ -142,6 +134,7 @@ To add support for a new network, update the `networks.json` file with the netwo
 ```
 
 Also, update the Jenkins pipeline choices to include the new network:
+
 ```groovy
 choice(
     name: 'networkName',