[aptos-cli] Update to 1.0.2

[gas] ChangeSet limits configurable on-chain

by introducing ChangeSetConfigs

Update blocks.md

[docs] Improved aggregator Move documentation (aptos-labs#5659)

* [docs] Improved aggregator documentation

* [docs] Typo fixes in aggregator documentation

* [docs] addressed comments

Devnet release for 01/12/2022

[e2e move tests] fix broken tests when running individually (aptos-la…

…bs#5705)

Clarify which endpoints return committed / pending transactions

[gha] Add credentials to build as well

[smoke tests] when getting "random" ports, use the filesystem to avoi…

…d conflicts between parallel test cases (processes) (aptos-labs#5421)

### Description

This should eliminate an entire class of smoke test flakiness in CICD due to conflicting ports.

Doing lsof on flaky tests in CICD, we observe that a new parallel test takes a port from a currently running node between the time it is stopped and started. When a node N goes down (by design, in the test) a port that was being used by that node N is stolen by a node M in another test. When node N restarts, the conflict occurs. (It seems very hard to hit if things were really random, yet in practice we see this at least once a day. Possibly the OS is prioritizing recently released ephemeral ports.)

cargo nextest runs parallel tests in different processes, so we need to avoid conflicts between processes. This introduces a counter file that keeps track of the last port used and a file for locking this to avoid races.

### Test Plan

Run smoke tests in CICD. Also run `cargo test` locally as a sanity check that the behavior is not changed for non-nextest uses.

Clean up wallet docs (aptos-labs#5525)

* Clean up wallet docs

* Delete yarn.lock

Co-authored-by: David Wolinsky <isaac.wolinsky@gmail.com>