Executable bit set on non-executable files

Similar to snaky_hash#1, our build system noticed some files have the executable bit set, but they shouldn't have it.

*** WARNING: ./opt/manageiq/manageiq-gemset/gems/version_gem-1.1.8/LICENSE.txt is executable but has no shebang, removing executable bit
*** WARNING: ./opt/manageiq/manageiq-gemset/gems/version_gem-1.1.8/CONTRIBUTING.md is executable but has no shebang, removing executable bit
*** WARNING: ./opt/manageiq/manageiq-gemset/gems/version_gem-1.1.8/SECURITY.md is executable but has no shebang, removing executable bit
*** WARNING: ./opt/manageiq/manageiq-gemset/gems/version_gem-1.1.8/lib/version_gem.rb is executable but has no shebang, removing executable bit
*** WARNING: ./opt/manageiq/manageiq-gemset/gems/version_gem-1.1.8/lib/version_gem/ruby.rb is executable but has no shebang, removing executable bit
*** WARNING: ./opt/manageiq/manageiq-gemset/gems/version_gem-1.1.8/lib/version_gem/error.rb is executable but has no shebang, removing executable bit
*** WARNING: ./opt/manageiq/manageiq-gemset/gems/version_gem-1.1.8/lib/version_gem/api.rb is executable but has no shebang, removing executable bit
*** WARNING: ./opt/manageiq/manageiq-gemset/gems/version_gem-1.1.8/lib/version_gem/basic.rb is executable but has no shebang, removing executable bit
*** WARNING: ./opt/manageiq/manageiq-gemset/gems/version_gem-1.1.8/lib/version_gem/rspec.rb is executable but has no shebang, removing executable bit
*** WARNING: ./opt/manageiq/manageiq-gemset/gems/version_gem-1.1.8/lib/version_gem/epoch.rb is executable but has no shebang, removing executable bit
*** WARNING: ./opt/manageiq/manageiq-gemset/gems/version_gem-1.1.8/CODE_OF_CONDUCT.md is executable but has no shebang, removing executable bit
*** WARNING: ./opt/manageiq/manageiq-gemset/gems/version_gem-1.1.8/README.md is executable but has no shebang, removing executable bit

Only a couple of these files actually have the executable bit set in the source (I'll make an MR for these). The rest must be getting changed somewhere in the gem package process, because if you download the gem package from rubygems.org they are all set there.