(dev/core#635) CRM_Utils_Cache::nack() - Fix format

[totten]

This is a follow-up to #13500.

Before

• CRM_Utils_Cache::nack() returns an array with a value named nack.
• The value returned is somewhat unique -- a random value is generated once per page-view.
• There is no explicit/direct unit-test.

After

• CRM_Utils_Cache::nack() returns a string.
• The value returned is more unique -- combining that random value (per page-view) and an offset (per invocation).
• There is an explicit/direct unit-test.

Comments

• The code was originally written with the intent of returning a string.
  However, there was a slight copy-paste error which caused it to return an
  array (which contained that string). Functionally, that worked (because
  the array met the same minimum uniqueness constraint and support comparison checks),
  but it's weird to read/inspect, and we should change quickly before
  something else locks-in the odd structure.

• The more unique the nack-value is, the more correct the nack-checking
  pattern is. Appending a static-counter is a simple, fast way to provide
  stronger uniqueness within a page-view.

• There may be some obscure edge-cases in which the previous pattern was not
  sufficiently unique -- e.g. combining tiers-of-tiers or
  decorators-of-decorators. I haven't verified that, but it seems
  unimportant given that the static-counter is so straightforward.

• In NaiveHasTrait, the extra ht suffix was an attempt to increase the
  uniquness. However, the static-counter seems better.

[civibot]

(Standard links)

• If this is your first pull-request for CiviCRM, please browse CONTRIBUTING.md for information about the development and testing processes.
• If you are reviewing this pull-request, you may wish to consult the test sites and the Review Standards (long template, short template).