Prune always removes GC lock

[ddanielr]

Describe the bug
The GC lock format includes additional information along with the host and port GC_CLIENT=<HostAndPort>
This causes the ZooZap code to always fail the hostPortPredicate check for the GC and attempt to remove the service lock on prune operations.

Versions (OS, Maven, Java, and others, as appropriate):

• Affected version(s) of this project: 2.1.4

To Reproduce
Steps to reproduce the behavior (or a link to an example repository that reproduces the problem):

1. start a running GC process
2. run ./accumulo-cluster prune --dry-run --gc
3. See the log message showing the lock will be deleted.

Expected behavior
The GC lock is correctly excluded

Additional context
This can be handled in the ZooZap code for removing the GC lock
See #6073 for additional info.