Determine strategy and resolve flaky tests.

[JonathanOppenheimer]

Currently there are two flaky test areas -- unit tests and the precompile e2e test.

These flaky tests prevent code from getting merged in frequently as they'll fail in CI.

precompile e2e:
See this issue for some logs: #1746. This is most likely caused by the updated npm versioning to resolve security vulnerabilities.

The best approach to fix this is to work on entirely getting rid of our reliance on npm.

unit tests:
Currently our approach to flaky unit tests isn't great as explained for reasons expounded upon in this PR: ava-labs/coreth#1065. While we should work on eliminating the flaky entirely in the interim we can improve the CI through one of the following approaches:

There are 3 possible approaches

1. Implement the logic at the gotest level as show in Optimize build_test.sh to not rereun tests on flake failure  coreth#1065
2. Implement the logic at the package level in go for flaky packages (@ARR4N suggestion)
3. Implement the logic at the unit test level for flaky tests using Bazel (@ARR4N suggestion)