Update and refactor hyrolo-tests.el

[matsl]

What

Update and refactor hyrolo-tests.el

• test/hyrolo-tests.el: Prefix all tests with hyrolo-tests. Use
  execute-kbd-macro instead of calling hact.
  (hyrolo-tests--add-items-interactive):
  (hyrolo-tests--hyrolo-grep-interactive): Add new separate test for
  interactive call.
  (hyrolo-tests--sort-test, hyrolo-tests--fgrep-find-all-types-of-files):
  Modify test to do both interactive and non-interactive call.
  (hyrolo-tests--fgrep-find-all-types-of-files): Use hy-delete-files-and-buffers.
  (hyrolo-tests--get-file-list): Use hy-delete-file-and-buffer.
  (hyrolo-tests--hyrolo-reveal-mode): Remove non-interactive guard.
  (hyrolo-tests--sort): Remove name suffix tests.

Why

While doing updates for interactive tests a set of small improvements
where found. This PR applies the updates into one PR with one commit.

[rswgnu]

@matsl , let's discuss and finalize tomorrow. I'd like to understand the trade-offs of switching from kbd-key to execute-kbd-macro.

[matsl]

let's discuss and finalize tomorrow. I'd like to understand the trade-offs of switching from kbd-key to execute-kbd-macro.

We did not discuss this in our last Talk. My thinking is like this:

• I started to use hact 'kbd-key by a coincident. At the time I did not know of any other way to do it and I had the examples with kbd-key from Hyperbole and used that.
• I have now realized that execute-kbd-macro works equally well. It seems by this experiment that the two ways are replaceable. So no functional difference.

Things I feel are better with execute-kbd-macro:

• It is a standard Emacs function.
• It is used for the same purposes by other programmers, like in Emacs source unit tests.
• It is cleaner since it does not involve or use the system under test (Hyperbole) for this.