fix(ingest): raise errors in more cases in rest sink

[gabe-lyons]

Rest sink would occasionally swallow HTTP errors. Now, if they get a 404 say, the rest sink outputs:

[2021-06-03 11:27:21,460] ERROR    {datahub.ingestion.run.pipeline:52} - failed to write record with workunit file://./examples/mce_files/bootstrap_mce.json:36 with 404 Client Error: Not Found for url: http://localhost:9002/entities?action=ingest and info {}

Checklist

• The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
• Links to related issues (if applicable)
• Tests for the changes have been added/updated (if applicable)
• Docs related to the changes have been added/updated (if applicable)

[hsheth2]

Since we're in except HTTPError as e:, we know that response.raise_for_status() will certainly throw here - probably want to remove that line since we already have it in e

We're actually not interested in the parse_exception since it just means that the response body wasn't json. Instead, we should set message to the response.text itself

[xiphl]

I encountered a case where I fed in a json MCE file to rest api. I then checked mysql, the entries did not make it into the database; but the entries were recorded into Elasticsearch.
I was wondering if this is related...
repeating the steps did the trick though.

[jjoyce0510]

@xiphl This is very concerning, and we've not seen it before. Please let us know if you experience this issue again

[shirshanka]

Closing as #2800 supercedes this.