Rename acceptance criteria

[leonlan]

This PR:

• Closes Rename RandomWalk and WorseAccept? #164.
• Adds and passes relevant tests.
• Has well-formatted code and documentation.

Notes:

• It is essential that you add a test when making code changes.
  This keeps the code coverage level up, and helps ensure the changes work as intended.
• When fixing a bug, you must add a test that would produce the bug in the master branch, and then show that it is fixed with the new code.
• New code additions must be well formatted. Changes should pass the pre-commit workflow, which you can set up locally using pre-commit.
• Docstring additions must render correctly, including escapes and LaTeX.

[codecov]

Codecov Report

Merging #167 (d223942) into master (db88880) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #167   +/-   ##
=======================================
  Coverage   99.46%   99.46%           
=======================================
  Files          30       30           
  Lines         748      748           
=======================================
  Hits          744      744           
  Misses          4        4           

Files Changed	Coverage Δ
alns/accept/AlwaysAccept.py	100.00% <100.00%> (ø)
alns/accept/MovingAverageThreshold.py	100.00% <100.00%> (ø)
alns/accept/RandomAccept.py	100.00% <100.00%> (ø)
alns/accept/__init__.py	100.00% <100.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[N-Wouda]

LGTM!