[FIX] web: cache rejected promises

[fw-bot]

Let's say we trigger two times a RPC that fails.

The first time, the cache is empty and we make the RPC. The ram cache is filled with prom.

The second time, we get prom from the ram cache.

When the RPC actually finishes, we end up in

.catch((error) => {
    this.ramCache.delete(table, key);
    def.reject(error);
});

=> the RPC failure is catched, which means prom itself is not rejected. Instead, it resolves with the result of .catch(...), which is undefined

Here is a simplified toy example:

const prom = Promise.resolve(
    Promise.reject(new Error("fetch failed")).catch(() => {})
);

In this example, prom is successful and the result is undefined

"

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:

---

I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: #238185
Forward-Port-Of: #237984

[robodoo]

[fw-bot]

@LucasLefevre @aab-odoo cherrypicking of pull request #237984 failed.

stdout:

CONFLICT (modify/delete): addons/web/static/src/core/utils/persistent_cache.js deleted in eea63f31d30e95617a38b1acf0e3da9a382edc0b and modified in 540bbffb23965d5228c0706475f2c5db3784c125.  Version 540bbffb23965d5228c0706475f2c5db3784c125 of addons/web/static/src/core/utils/persistent_cache.js left in tree.
CONFLICT (modify/delete): addons/web/static/tests/core/utils/persistent_cache.test.js deleted in eea63f31d30e95617a38b1acf0e3da9a382edc0b and modified in 540bbffb23965d5228c0706475f2c5db3784c125.  Version 540bbffb23965d5228c0706475f2c5db3784c125 of addons/web/static/tests/core/utils/persistent_cache.test.js left in tree.

Either perform the forward-port manually (and push to this branch, proceeding as usual) or close this PR (maybe?).

In the former case, you may want to edit this PR message as well.

⚠️ after resolving this conflict, you will need to merge it via @robodoo.

More info at https://github.com/odoo/odoo/wiki/Mergebot#forward-port

[LucasLefevre]

It's already working in 19.0 and covered by a test