Colored2 4.0.0 has incorrect permissions

[justinstoller]

Describe the Bug

Running r10k as a non-root user errors because of incorrect permissions in the Colored2 gem.

Expected Behavior

R10K works with non-root users (e.g. can be installed via puppet and then used by puppetserver).

Steps to Reproduce

Steps to reproduce the behavior:

1. Install r10k using /opt/puppetlabs/puppet/bin/gem
2. Configure puppetserver to use a code id script that looks like:
   /bin/bash
   /opt/puppetlabs/puppet/bin/r10k deploy display --fetch $1
3. Run the agent against the puppetserver. The server will throw a stacktrace failing to load Colored2 trying to find the code id of the catalog it is compiling. The server will be unable to serve catalogs until this is fixed.

Environment

R10K 5.0

Additional Context

I believe this isn't a huge issue to our users because most run r10k as part of their FOSS deployments as root and do not use code-id features. Code ids are used in PE but we build the colored2 gem ourselves in that case. I also believe once colored2 releases a new version of the gem with the correct permissions this will be resolved. However, we will still be vulnerable to regressions.

kigster/colored2#11