The output from getcap differs from previous releases

Issue

After upgrade or update to RHEL 8.6+ the output of getcap differs from the previous release.

Description extracted from the upstream commit:

While this does not change anything about the supported range of
equivalent text specifications for capabilities, as accepted by
cap_from_text(), this does alter the preferred output format of
cap_to_text() to be two characters shorter in most cases. That is,
what used to be summarized as:

   "= cap_foo+..."

is now converted to the equivalent text:

   "cap_foo=..."

which is also more intuitive.

That commit was part of the upstream release version 2.41 which was released on July 25th, 2020.
Those are the release notes for that upstream version:

- More man page fixes and improvements from Michael Kerrisk
- Minor optimization for cap_to_text() and (*cap.Set).String()
  - This lessens the number of characters (by 2) in a significant number of string representations.
  - In testing this, I found some differences between libcap and the Go package so fixed them and added a cap-compare test to validate equivalence.
- Discovered and added a missing function (*cap.Set).SetNSOwner() to achieve parity with libcap.