Using system tooling can lead to weird behavior of available Node
versions, for example this IPv6 resolution error:
```
[3/5] Fetching packages...
error Error: connect EHOSTUNREACH 2606:4700::6810:1922:443
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1495:16)
```
* chore: create a command for unified build and scrape flow
* chore: cleanup repo from temp folders
* feat: add new .md fetching mode
* feat: fetching through git added
* ci: add Scrape stage to the Jenkinsfile
* feat: add env variables to the Jenkinsfile
Use double branch setup with `master`/`develop` being built and pushed
as `deploy-master`/`deploy-develop`.
Signed-off-by: Jakub Sokołowski <jakub@status.im>
