test: beacon returning invalid address should revert

[Dozgor]

This test adds a scenario where the BeaconProxy is initialized with a beacon that returns an invalid (non-contract or null) implementation address.

Although the test causes Ethers.js to throw an error before reaching Solidity-level reverts, it helps highlight an edge case worth guarding against, as described in issue #5454.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2bda29a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR