Change FetchFeed consturctor to use named parameters

This way you can initialize the FetchFeed class with passing a custom
logger, but without having to pass a parser.
Add integration test for feed importing

Covers:
- Initial import
- Update where no new entries are available
- Update where new entries are available
Add integration test for feed with invalid pub dates
Change feed importer to use story ids to determine if a story is new

This should make feed importing more robust. Pub dates of feeds and
articles can not always be trusted (see
https://github.com/swanson/stringer/issues/261).
Using this mechanism we should always reliably be able to tell which stories
are new, regardless of pub dates being correctly reported or not.
Adhere to project code style (string double quotes)
Ignore stories older than 3 days when importing feeds

Timestamps in feeds can not be trusted but we not some form of
preventing old articles be imported when a new feed is added or when
this branch is merged and the way Stringer handles story updates
changes. See discussion in
https://github.com/swanson/stringer/issues/261 and
https://github.com/swanson/stringer/pull/328.
Allow to enforce SSL

Enabled when ENFORCE_SSL=true is set.
Merge pull request #333 from pascalw/feature-ssl-enforcement

Allow to enforce SSL
Merge pull request #328 from pascalw/feature-improve-feed-importing-robustness

Improve feed importing robustness
Remove foreman from Gemfile

> You should not put `foreman` into your `Gemfile` as the dependencies of a
> developer utility should not be able to interfere with the dependencies of
> your app.
<https://github.com/ddollar/foreman/pull/437#issuecomment-41110407>

> Ruby users should take care *not* to install foreman in their project's
> `Gemfile`.
<https://github.com/ddollar/foreman/blob/v0.68.0/README.md#installation>
Merge pull request #336 from Koronen/remove-foreman-from-gemfile

Remove foreman from Gemfile
Clean up Gemfile

* Sort gem declarations lexicographically.
* Use `arel` from RubyGems.org.
* Add pessimistic version lock on `rack-ssl`.

Fixes #334.
Merge pull request #338 from Koronen/clean-up-gemfile

Clean up Gemfile
Upgrade rack-protection to workaround issues with recent Chrome updates

Fixes https://github.com/swanson/stringer/issues/335
Merge pull request #339 from pascalw/bugfix-335-rack-protection

Upgrade rack-protection to workaround issues with recent Chrome updates
Replace highline dependency with standard Ruby

There are two minor differences from the `highline` version.

* Character echoing on password input has been disabled altogether.

  This is due to limitations of the `console/io` library.

* The password length validation has been removed.

  There's no feature like this in the `console/io` library and there's no
  validation like this on the model. Instead of reimplementing it, I think we
  might as well remove it.

The test for `ChangePassword` could use some improvement, especially to avoid
stubbing a method on the object under test.

The change to `ChangeUserPassword` is tangential, but fixes a bug where the
password wouldn't be updated due to a failing validation (`password` and
`password_confirmation` don't match).
Merge pull request #340 from Koronen/remove-highline-dependency

Replace highline dependency with standard Ruby
Update OpenShift Docs for Ruby 2.0 Cartridge

Update the instructions for OpenShift for the newly added Ruby 2.0
Cartridge. Due to an older version of Bundler, some workarounds have
to be included.
Set SECRET_TOKEN as OpenShift Environment Variable

This sets the SECRET_TOKEN variable as OpenShift Environment Variable,
rather than committing the SECRET_TOKEN to the repo.

[skip ci]
Merge pull request #342 from jasonngpt/updateOpenShiftDocs

Update OpenShift Docs for Ruby 2.0 Cartridge