The problem wasn't necessarily with the configuration of the Angular app or the SWA settings. But it was simply that we are using Enterprise-grade edge for the SWA, and somehow its cache was not cleared during the deployment of an Angular app update even though it should happen.

Clearing Enterprise-grade edge cache from the Azure portal resolved the issue:
https://portal.azure.com -> Open relevant Static Web App -> Enterprise-grade edge -> Purge