🧹 oft upgradeable example deploy script

[shankars99]

The old OFT Upgradeable deploy used to assume that the layerzero's internally defined network names founds under deployments https://www.npmjs.com/package/@layerzerolabs/lz-evm-sdk-v2?activeTab=code is the same as those defined in hardhat.config.ts's network config.

This isn't the case as developers can name networks differently.

Other examples https://github.com/LayerZero-Labs/devtools/blob/main/examples/oapp/deploy/MyOApp.ts use this pattern where we load the deployments (EndpointV2 among others) and artifacts into Hardhat in toolbox-hardhat

    // And we check the config for packages from which to import deployments as well
    const deploymentSourcePackages = layerZero?.deploymentSourcePackages ?? ['@layerzerolabs/lz-evm-sdk-v2']

    // Here we create our two config extenders, two curried functions
    // that accept hardhat user config and return a hardhat user config with external
    // artifacts and deployments configured
    const withArtifacts = withLayerZeroArtifacts(...artifactSourcePackages)
    const withDeployments = withLayerZeroDeployments(...deploymentSourcePackages)

For some reason this does not work with Upgradeable which could be due to some internal hardcoding or use of other packages.

The solution is to unabstract the abstraction created by the above code snippet and raw fetch the EndpointV2 information from the layerzero network name