Upgrade to latest Java-Utils; eliminate Guava usage

In this release, I upgraded to the latest release of Java-Utils, which allowed me to eliminate usage of Guava APIs. These really weren't doing very much for me, and including this library could cause mixed-version issues for client projects.

NOTE: This is a breaking change because I switched from using the Guava Optional class to the standard Java Optional class, and from using the Guava Function class to the standard Java Function class.

Java 11: Upgrade TestNG to v7.7.1 and SettingsAPI to 3.0.5

NOTE: This is a bifurcation point. Version 5.0.0 and up require Java 11; version 4.x releases will continue to support Java 8.

In this release, I upgraded to the latest release of TestNG (version 7.7.1). I also upgraded to the latest release of SettingAPI (version 3.0.5), which resolves a vulnerability in commons-text.

Java 8: Upgrade to latest SettingsAPI

NOTE: This is a bifurcation point. Version 4.x releases will continue to support Java 8; version 5.0.0 and up will require Java 11.

In this release, I upgraded to the latest release of SettingAPI (version 3.0.5), which resolves a vulnerability in commons-text.

Upgrade Java-Utils and Settings to latest releases

This release upgrade Java-Utils and Settings to the latest release - 3.1.1 and 3.0.2 respectively.

Update settings library

In this release, I updated to the latest settings library (3.0.1), which resolves an identified vulnerability.

Build for Java 8; upgrade dependencies and plugins

In this release, I finally dropped support for Java 7. By building this library for Java 8, I'm able to upgrade dependencies to newer versions that resolve identified vulnerabilities.

Upgrade to the latest dependencies

Upgrade to latest dependencies: Java-Utils (2.2.0), Settings (2.3.11), and TestNG (7.5 - Java 8+)
Bifurcate implementation for retry analyzer to work with revisions to TestNG API.

Upgrade TestNG to version 7.5

For the Java 8 variant of TestNG Foundation, we're now running with the latest TestNG release (version 7.5).

Add setting for retry exception logging

In this release, I added a setting to specify adding the stack trace from the exception that caused the test to fail to the retry notification. This enables users to acquire this information without the need set the logging level to DEBUG.

Retry: Fix auto-attach, log exception; fix project

In this release, I applied the same sorts of Gradle 7 compatibility updates that I applied recently to Selenium Foundation. I also added the exception message to the retry notification logging. In the process of testing that change, I discovered bugs in the auto-attach implementation for retry analyzers. I fixed these are added unit tests to cover this functionality.