Yea this is actually a problem across multiple PWA's.
I've experienced this even on SuperPWA on WordPress.
Yes it is possible to prevent any page from being cached, but it becomes more of a problem of Chrome working properly.
To compound the issue there is server side caching, client side caching (browser caching), and PWA Caching.
Another issues is this scenario... You don't include cache control headers, then you want to include them, but your page is cached in browser and PWA. You can't refresh the page until you clear out the old page that included cache control headers. Chrome Developer tools are helpful, but never shows the PWA cached content to be able to clear. There is an option for "Bypass Cache" on network tab, but doesn't work fully.
It is getting better, but there were some things I should have included and then clearing out current cache to include that becomes a complicated issues that has to be done over and over until its perfect.
My newest PWA's use Google Workbox for the Service Worker which is at the root of your website: service_worker.js
There is a section for not caching elements / links which is updated by the do not cache part on the service tab, but its unclear how well workbox handles not Caching.
I'll update all of this as soon as possible.