also need to add --profile (and prob other deploy options) to mud dev-contracts

can do env loading right after this line

dotenv.config({ path: [`.env.${profile}`] });

actually, it's unclear if that's the right path, because we will have already loaded .env into the env by then

if someone had PRIVATE_KEY set in .env it wouldn't be overridden by PRIVATE_KEY in .env.$profile

and if we use dotenv.config({ override: true, ... }) then we potentially override any env vars passed directly into the command like PRIVATE_KEY=... mud deploy

so may need to parse the profile arg earlier or move the dotenv.config(...) call later to include both env files at the same time