tests: fix test failure due to os.freemem() behaviour change in node v17.4.0

[trentm]

The update to libuv 1.43.0 changed the behaviour of os.freemem() on
Linux to report "MemAvailable" from /proc/meminfo rather than "MemFree".

Refs: #2530

(Most test runs for all PRs will fail when testing against node v17 until this is merged in.)

[ghost]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-01-20T10:07:01.340+0000

• Duration: 23 min 16 sec

• Commit: 1868d7e

Test stats 🧪

Test	Results
Failed	0
Passed	243027
Skipped	0
Total	243027

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• run module tests for <modules> : Run TAV tests for one or more modules, where <modules> can be either a comma separated list of modules (e.g. memcached,redis) or the string literal ALL to test all modules

• run benchmark tests : Run the benchmark test only.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)