Deprecate bytecode for deployedBytecode in setCode action.

[roninjin10]

I believe viem should deprecate bytecode and instead use deployedBytecode

import { testClient } from './client'
 
await testClient.setCode({ 
  address: '0xe846c6fcf817734ca4527b28ccb4aea2b6663c79',
  - bytecode: '0x60806040526000600355600019600955600c80546001600160a01b031916737a250d5630b4cf539739df...'
  + deployedBytecode: '0x60806040526000600355600019600955600c80546001600160a01b031916737a250d5630b4cf539739df...'
})

Why

When solidity contracts are compiled they compile into bytecode and deployedBytecode. Bytecode is the code that runs when you deploy the contract to the chain. DeployedBytecode is the final result of the bytecode that actually ends up at the contract address after executing the deployment.

Because viem calls it bytecode it can be confusing which one you should use. For example, if you are looking at foundry artifacts you might incorrectly copy the json value bytecode when you should be copying deployedBytecode

Selfishly this makes it work way better with tevm too

import {TevmContract} from './TevmContract.js'
import {testClient} from './testClient.js'

// this only works if the prop is called `deployedBytecode`
await testClient.setCode(TevmContract)

// otherwise it looks like this
await testClient.setCode({
  address: TevmContract.address,
  bytecode: TevmContract.deployedBytecode,
})

Solution

1. Deprecate bytecode but keep it around for a bit so it's not a breaking change. Add new deployedBytecode property
2. Remove bytecode in a future major release