Do not treat warnings as errors while coding

[nulltoken]

Pull request description

PR meta checklist

• [x] Pull request is targeted at main branch for code
• [ ] Pull request is linked to all related issues, if any.

Code PR specific checklist

• [x] My code follows the code style of this project and AspNetCore coding guidelines.
• [ ] My change requires a change to the documentation.
  • [ ] I have updated the documentation accordingly.
• [ ] I have updated the appropriate sub section in the CHANGELOG.md.
• [ ] I have added, updated or removed tests to according to my changes.
  • [ ] All tests passed.

:wave: This one is a very minor one. It actually aims at making the project a bit easier to onboard.

The rationale being, while working on a contribution, I'm not sure pestering the developer about XML comments and code style is the best approach. The proposal is to relax the "WarningsAsErrors" rule while coding.

As the CI is configured to build in Release mode, those warnings will eventually be fixed in order to get the pull request merged.

But it will allow one to scratch an itch, play with NCronJob code without cursing too much at the compiler while spiking something :wink:

[linkdotnet]

You are absolutely right and I appreciate the PR.