Fix check bom http error reporting

[gernot-h]

As reported by @rfuentess in #227, the current HTTP response evaluation in "bom check" was wrong leading to incomplete error output on e.g. HTTP 403:

Loading SBOM file /home/gernot/checkout/capycli/tests/fixtures/sbom_with_sw360.json
  4 components  read from SBOM
  Not found colorama, 0.4.6, 9a2373710bd44769a2560dd31280901d
  Error retrieving release data: 
  python, 3.8, 05c30bf89a512463260b57e84d99b38f

This PR fixes it as suggested by Raul so errors are printed as intended:

Loading SBOM file /home/gernot/checkout/capycli/tests/fixtures/sbom_with_sw360.json
  4 components  read from SBOM
  Not found colorama, 0.4.6, 9a2373710bd44769a2560dd31280901d
  Error retrieving release data: 
  python, 3.8, 05c30bf89a512463260b57e84d99b38f
  Status Code: 403

While SW360 usually doesn't answer with HTTP 403 (to my knowledge), we should still be prepared for it - and the fix will also help reporting a HTTP token which gets invalid while CaPyCli runs (resulting in HTTP 401) which is probably what Raul observed.

[gernot-h]

Claude Opus identified a comparable problem in create_project.py which should now also be fixed.

[tngraf]

Why has this code been removed?
response.text is one possible problem description.
SW360s real description is in swex.details["error"] and swex.details["message"]

[gernot-h]

This is the current control flow from https://github.com/sw360/capycli/blob/v2.11.1/capycli/project/create_project.py#L139:

            if swex.response is None:  # 1
                ...
                sys.exit(...)
            if swex.response.status_code == requests.codes["unauthorized"]:  # 2
                ...
                sys.exit(...)
            if swex.response.status_code == requests.codes["forbidden"]:  # 3
                ...
                sys.exit(...)
            if swex.response:  # 4
                ...
                sys.exit(...)
            if swex.details:  # 5
                ...
                sys.exit(...)

            print_red("  Unknown error ...)  # 6
            sys.exit(...)

Now as in the other error described by Raul, # 4 will never be triggered as .response will evaluate to False for any HTTP error. So we would need to replace # 4 by if swex.response is not None which is what I did first. But then# 4 is the exact opposite of # 1, so mypy shouted at me that neither # 5 nor # 6 are reachable.

Or in other words: # 1 is already the "general error" part which is called when we have no valid .response, so we don't need # 6.

And looking into https://github.com/sw360/sw360python/blob/master/sw360/sw360error.py, swex.details is only populated when we have a valid .response, so # 4 will already cover that case, so we also don't need # 5.

Or do I overlook something?

[gernot-h]

The patch is also somewhat confusing, but what I actually did was removing # 5 and # 6 and making the code from # 4 the fall-back if other if's don't mach.