Assign envs before preload

Currently ENV's of the client are not up to date during initialization of the app.

When having the following in `config/application.rb`
```ruby
...
    config.force_ssl = !!ENV['FORCE_SSL']
...
```
The following occurs:
1) `FORCE_SSL=1 RAILS_ENV=test bin/rails runner 'p Rails.application.config.force_ssl' # => true`
2) `RAILS_ENV=development bin/rails runner 'p Rails.application.config.force_ssl' # => true`

If you reverse these steps, the result for both steps would be `false`.

Obviously we want 1 to yield true, and 2 to yield false.
What does this protect against? I'm just concerned about whether this will lead to potential confusion. If someone is fiddling with these vars maybe it's better to just assume they know what they're doing. But maybe you envisaged a scenario where not excluding these vars will cause particular problems?