Bugfix: Special Regex characters caused values to not encrypt

Due to the way we were looking for existing lines in a settings file, which was
basically interpolating the settings name/value into a `Regexp`, if the name or
value had any special regex characters such as '+', '\', etc, they were treated
as part of the regex instead of as literal characters.

Therefore, this settings file:

```yaml
my_setting:
  _secure_has_a_special+_char: "My value is special?"
```

would not properly encrypt.

Now we are escaping both the name and the value before putting it into the regex
and it works fine.

--------------------------------------------------------------------------------
Branch:        bug/names-and-values-with-regex-chars-do-not-encrypt
Signed-off-by: Jeff Felchner <accounts+git@thekompanee.com>
Merge branch 'bug/names-and-values-with-regex-chars-do-not-encrypt'
Ensure Chamber loads Chamber::Instance in bin/chamber

The problem is that
https://github.com/thekompanee/chamber/blob/master/lib/chamber/commands/initialize.rb#L13
calls `Chamber.configuration` which is part of the `Chamber::Instance` class
that the `Chamber` singleton delegates to via method_missing. Since the
`bin/chamber` file only includes `chamber/binary/runner`, the `Chamber`
singleton is never correctly initiated.

Actions:
  Fixes #29
Merge branch 'ted27-patch-1'
Version Bump to 2.3.2
Docs: Add CHANGELOG
Allow hashie to be upgraded to 3.x
Chore: Add .rubocop.yml
Version Bump to 2.4.0
Docs: Add v2.4.0 CHANGELOG notes

--------------------------------------------------------------------------------
Change-Id:     I96b8238ea3e02b8decb23f20b6eaf1631688618d
Signed-off-by: Jeff Felchner <accounts+git@thekompanee.com>
Chore: Update gitignore to latest version
Chore: Update rubocop config
Feature: Allow host settings to override environment settings in Rails

Now, when you boot your app in Rails, it's possible to set local settings which
only apply to your current machine in your YAML files.

For instance if, in development, you use a local proxy like POW and prefer to
access the site from 'myapp.local.dev', then you can set that in your local
settings and it will work without a problem.

Implement like so:

```yaml
my_hostname:
  http:
    host: myapp.local.dev
```

--------------------------------------------------------------------------------
Change-Id:     I8eec29aedf825e0b4e16d4a8664b302dfed48f59
Signed-off-by: Jeff Felchner <accounts+git@thekompanee.com>
Style: Change to Ruby 1.9 hash syntax

--------------------------------------------------------------------------------
Signed-off-by: Jeff Felchner <accounts+git@thekompanee.com>
Style: Remove spaces from inside parenthesis

--------------------------------------------------------------------------------
Signed-off-by: Jeff Felchner <accounts+git@thekompanee.com>
Style: Fix trailing commas

--------------------------------------------------------------------------------
Signed-off-by: Jeff Felchner <accounts+git@thekompanee.com>
Style: Fix spaces inside brace literals

--------------------------------------------------------------------------------
Signed-off-by: Jeff Felchner <accounts+git@thekompanee.com>
Chore: Add rubocop_todo.yml
Style: Fix word arrays by converting to %w

--------------------------------------------------------------------------------
Signed-off-by: Jeff Felchner <accounts+git@thekompanee.com>
Style: Fix spaces inside brackets

--------------------------------------------------------------------------------
Signed-off-by: Jeff Felchner <accounts+git@thekompanee.com>