feat: allow cert caching if local storage is defined

[joshLong145]

Description

Changes a conditional check for storing AMD SEV SNP certificates in localstorage to now check if the api is available rather than doing a check for a browser environment. this will allow for caching in local storage in non browser environments if the api is available.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

A new connection e2e test has been added which defines a localstorage provider and checks that certs have been cached after connect finishes.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[Ansonhkg]

Nice! e2e seems to be failing though with your cert test

❌ 1 test(s) failed
-------------------
- [1] Error happened in /home/runner/work/js-sdk/js-sdk/e2e-nodejs/group-connection/test-connection-cert-caching.mjs, see below for details 👇 
Error: missing revert data in call exception; Transaction reverted without a reason string [ See: https://links.ethers.org/v5-errors-CALL_EXCEPTION ] (data="0x", transaction={"to":"0xBC7F8d7864002b6629Ab49781D5199C8dD1DDcE1","data":"0x43cb0a0e","accessList":null}, error={"reason":"missing response","code":"SERVER_ERROR","requestBody":"{\"method\":\"eth_call\",\"params\":[{\"to\":\"0xbc7f8d7864002b6629ab49781d5199c8dd1ddce1\",\"data\":\"0x43cb0a0e\"},\"latest\"],\"id\":45,\"jsonrpc\":\"2.0\"}","requestMethod":"POST","serverError":{"errno":-104,"code":"ECONNRESET","syscall":"read"},"url":"https://chain-rpc.litprotocol.com/http"}, code=CALL_EXCEPTION, version=providers/5.7.2)

[joshLong145]

Nice! e2e seems to be failing though with your cert test

❌ 1 test(s) failed
-------------------
- [1] Error happened in /home/runner/work/js-sdk/js-sdk/e2e-nodejs/group-connection/test-connection-cert-caching.mjs, see below for details 👇 
Error: missing revert data in call exception; Transaction reverted without a reason string [ See: https://links.ethers.org/v5-errors-CALL_EXCEPTION ] (data="0x", transaction={"to":"0xBC7F8d7864002b6629Ab49781D5199C8dD1DDcE1","data":"0x43cb0a0e","accessList":null}, error={"reason":"missing response","code":"SERVER_ERROR","requestBody":"{\"method\":\"eth_call\",\"params\":[{\"to\":\"0xbc7f8d7864002b6629ab49781d5199c8dd1ddce1\",\"data\":\"0x43cb0a0e\"},\"latest\"],\"id\":45,\"jsonrpc\":\"2.0\"}","requestMethod":"POST","serverError":{"errno":-104,"code":"ECONNRESET","syscall":"read"},"url":"https://chain-rpc.litprotocol.com/http"}, code=CALL_EXCEPTION, version=providers/5.7.2)

Did a re run of that job since the error looked to be an rpc timeout issue. The e2e tests now pass.

[Ansonhkg]

lgtm

[glitch003]

looks good - just the one change in the test so that when we start supporting Genoa, or if the AMD URL path changes, the test doesn't break.

[joshLong145]

@glitch003
Can you re review?