feat(attachments): log warning if POST attachment returns 202

[deveaud-m]

Not sure if throwing an error is the right thing to do here but not informing the client, that the upload couldn't be performed is not a good choice. Since there is no logging configured in this module, I went for raising ;)

The API documentation released on SW360 servers is unfortunately not very verbose when it comes to POST responses for the /attachments endpoints, so I wrote a test based on experimental data.

Closes #17

[gernot-h]

@deveaud-m, thank you for the PR! However, I don't really agree here. HTTP 202 means that "The request has been accepted for processing, but the processing has not been completed.". I assume the SW360 developers deliberately chose a return code in the "2xx success" range, so we should also consider it a success.

Judging from your test case, I guess this is because you're uploading to an existing release but you have no clearing admin rights in SW360. So it doesn't mean that the upload wasn't performed, it's just waiting for confirmation from the release owner. So I think an exception is not the way to react on this.

There's nothing you as user can do to fix it.

@tngraf, what do you think?

[deveaud-m]

Judging from your test case, I guess this is because you're uploading to an existing release but you have no clearing admin rights in SW360. So it doesn't mean that the upload wasn't performed, it's just waiting for confirmation from the release owner. So I think an exception is not the way to react on this.

I was expecting this feedback.

We need at least to inform the client that a moderation request has been created but there is no logging in this python module and using a print() is not ideal.

@gernot-h What would you propose?

[gernot-h]

Sorry, I've seen #17 too late, we should probably continue discussion there.

[deveaud-m]

@gernot-h @tngraf patch has been updated according to your feedback from #17