fix: deploy new factory with old sso beacon

The problem was in the upgrade process a new SSO beacon proxy was
deployed for the new implemention instead of re-using the existing one.
This was because it used the era-sepolia.json which only contains the
contracts necessary for the auth-server and didn't have the SSO Beacon
address.
The SSO beacon address needs to stay the same because its address is
specifically allowed by the sequencer.

Might also need to update + fund the paymaster, will test in PR.

Author: cpb8010

packages/auth-server/stores/era-sepolia.json

@@ -1,7 +1,7 @@
 {
   "session": "0x64Fa4b6fCF655024e6d540E0dFcA4142107D4fBC",
   "passkey": "0x006ecc2D79242F1986b7cb5F636d6E3f499f1026",
-  "accountFactory": "0xd122999B15081d90b175C81B8a4a9bE3327C0c2a",
+  "accountFactory": "0x7230ae6D4a2C367ff8493a76c15F8832c62f9fE9",
   "accountPaymaster": "0x4Cb1C15710366b73f3D31EC2b3092d5f3BFD8504",
   "recovery": "0x6AA83E35439D71F28273Df396BC7768dbaA9849D",
   "recoveryOidc": "0x116A07f88d03bD3982eBD5f2667EB08965aAe98c",