testbsd-x5: Use scraping to get latest version of node/npm

In FreeBSD VM hosted on Google GCE, with `pkg search` command, it fails
to retrieve the latest list even after `pkg update -f` with `latest`
repository selected (checked with `pkg -vv search`). There seems to be
some caching mechanism involved, which I couldn't find a way to avoid.

testbsd-x4: Use scraping to get latest version of node/npm

In FreeBSD VM hosted on Google GCE, with `pkg search` command, it fails
to retrieve the latest list even after `pkg update -f` with `latest`
repository selected (checked with `pkg -vv search`). There seems to be
some caching mechanism involved, which I couldn't find a way to avoid.

x3 custom release (idempotency test)

created by human being (not the CI automation)

testbsd-x2: Use scraping to get latest version of node/npm

In FreeBSD VM hosted on Google GCE, with `pkg search` command, it fails
to retrieve the latest list even after `pkg update -f` with `latest`
repository selected (checked with `pkg -vv search`). There seems to be
some caching mechanism involved, which I couldn't find a way to avoid.

testbsd-x1: Use scraping to get latest version of node/npm

In FreeBSD VM hosted on Google GCE, with `pkg search` command, it fails
to retrieve the latest list even after `pkg update -f` with `latest`
repository selected (checked with `pkg -vv search`). There seems to be
some caching mechanism involved, which I couldn't find a way to avoid.

testbsd8

Create publish task

testbsd7

Create publish task

testbsd20

~wip~test with bash

testbsd2

Create publish task

testbsd19

~wip~test with bash