security: avoid compromised release being publish through the poisoned cache (#1458)

## 📜 Description

Don't use `cache` for publish job.

## 💡 Motivation and Context

Based on
https://github.com/actions/setup-node/issues/1445#issuecomment-4040130833

## 📢 Changelog

<!-- High level overview of important changes -->
<!-- For example: fixed status bar manipulation; added new types
declarations; -->
<!-- If your changes don't affect one of platform/language below - then
remove this platform/language -->

### CI

- do not use cache for publishing (to avoid poisoned cache vector
attack);

## 🤔 How Has This Been Tested?

There is no way to test it at the moment 😅 

## 📝 Checklist

- [x] CI successfully passed
- [x] I added new mocks and corresponding unit-tests if library API was
changed