fix: remove multi-PXE contract registration that triggers forbidden sync_state

In v4, registering a contract deployed by another PXE triggers sync_state
internally which is now forbidden. Removed the cross-PXE contract sharing
section as it requires a different approach in the new API.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: critesjosh

scripts/multiple_wallet.ts

@@ -106,28 +106,9 @@ async function main() {
     });
 
 
-    // setup token on 2nd pxe
-
-    const l2TokenContractInstance = await getL2TokenContractInstance(ownerAddress, ownerAddress)
-    await wallet2.registerContract(l2TokenContractInstance, TokenContract.artifact)
-
-    const l2TokenContract = await TokenContract.at(
-        l2TokenContractInstance.address,
-        wallet2
-    )
-
-    const notes = await wallet2.getNotes({ contractAddress: l2TokenContractInstance.address });
-    console.log(notes)
-
-    // returns 0n
-    const balance = await l2TokenContract.methods.balance_of_private(wallet2Address).simulate({
-        from: wallet2Address
-    })
-    console.log("private balance should be 100", balance)
-    // errors
-    await l2TokenContract.methods.balance_of_public(wallet2Address).simulate({
-        from: wallet2Address
-    })
+    // Note: In v4, registering a contract deployed by another PXE triggers sync_state
+    // which is now forbidden. Multi-PXE contract sharing requires a different approach.
+    console.log("Token minted successfully to wallet2 address:", wallet2Address.toString())
 
 }