Fix bogus bundler requirement in puppetserver-ca

When developing, you are intended to explicitly use bundler by running
`bundle exec exe/puppetserver-ca`, not by running `./exe/puppetserver-ca`
and hoping for the bundle to be loaded for you.

Because this file is included as-is in the gem, when executed from the
outside of a bundle, this result in an error:

```sh-session
$ /opt/puppetlabs/puppet/lib/ruby/vendor_gems/gems/openvoxserver-ca-3.0.0/exe/puppetserver-ca
/opt/puppetlabs/puppet/lib/ruby/vendor_gems/gems/openvoxserver-ca-3.0.0/exe/puppetserver-ca:6:in `<main>': private method `require' called for Bundler:Module (NoMethodError)

Bundler.require(:default)
       ^^^^^^^^
```

On an AIO installation, users are unlikely to hit this issue (given the
complex path above).  But on FreeBSD, this puppetserver-ca "entry point"
is in the $PATH (maybe I should not install it), so easily found by
users, which then expect it to work.

Author: smortex

exe/puppetserver-ca

@@ -1,10 +1,5 @@
 #!/usr/bin/env ruby
 
-# This requires everything in our Gemfile, so when functionally testing
-# our debugging tools are available without having to require them
-require 'bundler/setup'
-Bundler.require(:default)
-
 require 'puppetserver/ca/cli'
 
 exit Puppetserver::Ca::Cli.run(ARGV)