NuGet issues aka `PublishToNuget` release target task

[raman-m]

Predecessor

• 2088

• Release Tag: 23.3.0

Actual Behavior

The last release, build 4186, failed due to the absence of DevOps for NuGet, leading to the manual publication of the Ocelot NuGet package. Consequently, the remaining packages were not published at all.

TODO

• [x] Administration: Acquire ownership of all Ocelot.* packages under the ThreeMammals NuGet organization. Done on Jun 10 ✔️
• [x] Administration: Manually upload all packages from Release Assets. Done! Check list ✔️
• [x] Mark the 23.3.0 release as the Latest one. Done on June 10 ✔️
• [x] DevOps: Generate a new NuGet API token for the ThreeMammals Package Owner. Done on June 10 ✔️
• [x] DevOps: Establish a new CircleCI environment variable. Done on June 10 ✔️
• [x] DevOps: Revise the build.cake script with new variables and a new Release Engineer user. Done → Commit https://github.com/ThreeMammals/Ocelot/commit/58727316dbaba0adb8182aa1d51dc21bd1ca61b6 ✔️
• [x] DevOps: Conduct a technical release to verify the new automation setup and configurations.
• [X] Release: Issue an official Patch release, v23.3.1, as a non-technical update. Done on June 11 → 23.3.3 ✔️

Specifications

• Version: 23.3.0

[raman-m]

Fixed in commit https://github.com/ThreeMammals/Ocelot/commit/8c0180a6461984ebd11ceca5544ca9d0e1564975 ✔️ Release: 23.3.3 Published package: Ocelot.23.3.3