Fix resolve implementation (#8413)

<!--

## title your PR with this format: "[SDK/Dashboard/Portal] Feature/Fix: Concise title for the changes"

If you did not copy the branch name from Linear, paste the issue tag here (format is TEAM-0000):

## Notes for the reviewer

Anything important to call out? Be sure to also clarify these in your comments.

## How to test

Unit tests, playground, etc.

-->

<!-- start pr-codex -->

---

## PR-Codex overview
This PR focuses on improving the `resolveImplementation` function in the `thirdweb` package by enhancing the implementation resolution process for proxy contracts.

### Detailed summary
- Replaced the existing implementation resolution logic with a more robust approach using `Promise.all` to fetch implementations from both storage and contract calls.
- Introduced a loop to handle multiple implementations, ensuring that valid addresses are checked before proceeding.
- Updated the return logic to ensure correct addresses and bytecode are returned based on the resolved implementation.

> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`

<!-- end pr-codex -->

<!-- This is an auto-generated comment: release notes by coderabbit.ai -->

## Summary by CodeRabbit

* **Bug Fixes**
  * Improved the reliability of contract implementation resolution to handle edge cases more robustly when detecting implementations across proxy contracts and various contract architecture types. Processing is now more efficient through concurrent implementation detection and optimized fallback handling, ensuring more consistent and faster results in complex contract scenarios.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Author: kumaryash90

.changeset/afraid-regions-push.md

@@ -0,0 +1,5 @@
+---
+"thirdweb": patch
+---
+
+Resolve implementation from contract call

packages/thirdweb/src/utils/bytecode/resolveImplementation.ts

@@ -47,42 +47,43 @@ export async function resolveImplementation(
   }
 
   // check other proxy types
-  let implementationAddress: string | undefined;
-
   if (beacon && beacon !== AddressZero) {
     // In case of a BeaconProxy, it is setup as BeaconProxy --> Beacon --> Implementation
     // Hence we replace the proxy address with Beacon address, and continue further resolving below
     contract = getContract({
       ...contract,
       address: beacon,
     });
-
-    implementationAddress = await getImplementationFromContractCall(contract);
-  } else {
-    implementationAddress = await getImplementationFromStorageSlot(contract);
   }
 
-  if (
-    implementationAddress &&
-    isAddress(implementationAddress) &&
-    implementationAddress !== AddressZero
-  ) {
-    const implementationBytecode = await getBytecode({
-      ...contract,
-      address: implementationAddress,
-    });
-    // return the original contract bytecode if the implementation bytecode is empty
-    if (implementationBytecode === "0x") {
+  const implementations = await Promise.all([
+    getImplementationFromStorageSlot(contract),
+    getImplementationFromContractCall(contract),
+  ]);
+
+  for (const implementationAddress of implementations) {
+    if (
+      implementationAddress &&
+      isAddress(implementationAddress) &&
+      implementationAddress !== AddressZero
+    ) {
+      const implementationBytecode = await getBytecode({
+        ...contract,
+        address: implementationAddress,
+      });
+      // return the original contract bytecode if the implementation bytecode is empty
+      if (implementationBytecode === "0x") {
+        return {
+          address: contract.address,
+          bytecode: originalBytecode,
+        };
+      }
+
       return {
-        address: contract.address,
-        bytecode: originalBytecode,
+        address: implementationAddress,
+        bytecode: implementationBytecode,
       };
     }
-
-    return {
-      address: implementationAddress,
-      bytecode: implementationBytecode,
-    };
   }
 
   return { address: contract.address, bytecode: originalBytecode };