chore: allow deletion of selected network

[Teng-Web3]

Explanation

The Global Network Selector is being removed In the new version of extension, we can select muti active networks, so we can remove any of them including the current(selected) one.

References

Fix : #6162
Related to: MetaMask/metamask-extension#34457

Changelog

After change

after_change.mp4

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed, highlighting breaking changes as necessary
• I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes

[cursor]

Bug: Network Deletion Bug Causes Inconsistent State

Removing the check that prevented deletion of the currently selected network causes selectedNetworkClientId to point to a non-existent network, leading to an inconsistent state. The subsequent logic, designed for deleting an EVM network when a non-EVM network is selected, now incorrectly executes when deleting any currently selected network (including EVM), potentially causing unintended behavior like an automatic switch to EVM mainnet. The associated comment is also misleading.

packages/multichain-network-controller/src/MultichainNetworkController/MultichainNetworkController.ts#L202-L206

core/packages/multichain-network-controller/src/MultichainNetworkController/MultichainNetworkController.ts

Lines 202 to 206 in a95fb1a

	if (selectedChainId === hexChainId) {
	// If a non-EVM network is selected, we can delete the currently EVM selected network, but
	// we automatically switch to EVM mainnet.
	const ethereumMainnetHexChainId = '0x1'; // TODO: Should probably be a constant.

packages/network-controller/src/NetworkController.ts#L2353-L2363

core/packages/network-controller/src/NetworkController.ts

Lines 2353 to 2363 in a95fb1a

	const autoManagedNetworkClientRegistry =
	this.#ensureAutoManagedNetworkClientRegistryPopulated();
	const networkClientOperations =
	existingNetworkConfiguration.rpcEndpoints.map((rpcEndpoint) => {
	return {
	type: 'remove' as const,
	rpcEndpoint,
	};
	});

---