Use an in-memory sqlite database in test mode.

This speeds up the tests a bit without any tradeoff that I am aware of.
Fixing specs which were trying to make net calls
Ignore crt files.
Update Rails to 4.1.7
Merge pull request #235 from CenturyLinkLabs/chore/in-memory-test-db

Use an in-memory sqlite database in test mode.
Write certificate on read instead of write.
[#81019816]
Ensure the contents are actually persisted in the temp file.
[#82238400]
Split DeploymentTarget.deployments into a module.

I'm about to add another related resource for metadata, so this seemed
like a good idea. There were a number of things at the top of the test
that only pertained to the deployments resource, so that is probably
easier to read now. I almost moved the cert-related items into their own
concern but stopped myself.
Add deployment target metadata refresh endpoint.

So there's a lot going on here. Agents can return their metadata, which
includes the metadata from their connected adapter. This involves a lot
of requests when you go from the UI all the way to the adapter, so we
want to persist it. There are two models that can be easily confused but
are distinct. RemoteAgentMetadata is an ActiveResource model that talks
to the remote agent, and DeploymentTargetMetadata is the persistence in
the API.

ActiveResource was not particularly pleased with the idea of a dynamic
endpoint (because each agent has metadata at a different URL) combined
with a singleton (because each endpoint only has one metadata), nor was
it thrilled with a dynamic resource having embedded resources within it
(the RemoteAgentMetadata includes separate hashes for the agent and the
adapter rather than a flat list). Most of the extra code in the
ActiveResource models is to deal with that.
Add metadata to serialized DeploymentTarget.
Nest metadata within metadata refresh response.

This accomplishes two things: it makes room for success/error
information in our response, and makes this endpoint easier to use in
ActiveResource. It's going to be hard to 'create' a refresh but return a
metadata object. If the refresh object that is returned contains
metadata, though, that jives better with ActiveResource.
Remove HTML representation of deployment target refresh.

This doesn't serve HTML, I was getting my responsibilities mixed up
again. When I first wrote this, I thought the browser would be hitting
this directly to avoid writing a proxy to it on the UI.