feat(web-contents): add bypassCache option to navigationHistory.restore

[panther7]

Description of Change

navigationHistory.restore() currently loads the restored entry via LoadIfNecessary(), which serves the page from the HTTP cache without contacting the server. This means that conditions requiring a live network request — such as an expired or changed TLS certificate — are not re-evaluated and the corresponding events (e.g. certificate-error) are never fired.

This PR adds an optional bypassCache boolean parameter (default false) to navigationHistory.restore(). When set to true, the restored entry is loaded via content::ReloadType::BYPASSING_CACHE instead of LoadIfNecessary(), forcing a fresh network request so that certificate errors and other network failures surface normally.

Before:

await contents.navigationHistory.restore({ entries, index });
// TLS certificate is never re-checked — certificate-error won't fire

After:

await contents.navigationHistory.restore({ entries, index, bypassCache: true });
// Forces a network request — certificate-error fires if cert is invalid/expired

Checklist

• I have built and tested this change
• I have filled out the PR description
• I have reviewed and verified the changes
• npm test passes
• tests are changed or added
• relevant API documentation, tutorials, and examples are updated and follow the documentation style guide
• PR release notes describe the change in a way relevant to app developers, and are capitalized, punctuated, and past tense.

Release Notes

Notes: Added bypassCache option to navigationHistory.restore() to force a fresh network request when restoring navigation history, allowing certificate errors and other network failures to surface normally.

[panther7]

Tested on Windows and 42-x-y branch.