Allow overriding the type of the default network

[fvictorio]

This fixes #7795, but I'm not fully convinced about the change.

The problem is that we are always setting the type of default network to be a simulated network, and we also set some other default values. This makes sense, but it does seem to assume that the network is not of type http. My concern is that a user's settings could interact in the wrong way with those default values.

On the other hand, without this change there's no way to have an http network as the default network, something that was possible in HH2.

One alternative here is to re-introduce the defaultNetwork config, and default it to "default" (yes).

Another alternative is to only use those default values if the user doesn't change the type, but that starts feeling a bit too complex.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 30241c0

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

[kanej]

We should double check running tests against a npx hardhat node instance, and add a changeset.
But in principle we are happy with this approach to let users set default to an http network.

[michalbrabec]

Overriding the default network creates the need to setup a new network for npx hardhat node and then used it with the --network parameter.
#7795 (comment)