Accept more HTTP response codes

[nosnilmot]

Only consider HTTP response codes >= 400 as errors, avoiding unnecessary retries and potential duplicates

Fixes #356

Note: this is NOT a full fix for Microsoft's deprecation of Office 365 connectors for Teams, but is sufficient to allow use of powerautomation workflow to adapt the existing message content.

Testing done

it compiles and passes existing unit tests

Submitter checklist

• [x] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• [x] Ensure that the pull request title represents the desired changelog entry
• [x] Please describe what you did
• [x] Link to relevant issues in GitHub or Jira
• [x] Link to relevant pull requests, esp. upstream and downstream changes
• [x] Ensure you have provided tests - that demonstrates feature works or fixes the issue

[damianszczepanik]

New version is release, you can update and check

[nosnilmot]

New version is release, you can update and check

The latest version offered by Jenkins is still 4.21.1 (in https://updates.jenkins.io/current/update-center.json), is there another step necessary to make 4.21.2 generally available?

[damianszczepanik]

You are right and thanks for letting me know. I see another plugin has same problem - SNAPSHOT version is published instead of final one. New version should be available soon as is hopefully correctly deployed https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/Office-365-Connector/4.21.5/ and the reason of invalid version was this commit https://github.com/jenkinsci/office-365-connector-plugin/commit/6ee69d944807886802671f0ef5424a3bc991c6bc that introduces double SNAPSHOT - still don't know why as the release process did not change but the dependencies were updated