add(chain): Adds a network_name field to testnet::Parameters

[arya2]

Motivation

We want to allow for configuring the network name so that cached chain states for different networks are stored separately and configured network names can be displayed in Zebra's logs or elsewhere.

Closes #8327.

Depends-On: #8383.

PR Author Checklist

Check before marking the PR as ready for review:

• Will the PR name make sense to users?
• Does the PR have a priority label?
• Have you added or updated tests?
• Is the documentation up to date?

For significant changes:

• Is there a summary in the CHANGELOG?
• Can these changes be split into multiple PRs?

If a checkbox isn't relevant to the PR, mark it as done.

Solution

• Adds network_name fields to testnet::Parameters and ParametersBuilder
  • Sets default network name to Testnet and default configured Testnet name to UnknownTestnet
• Adds accessor method for testnet::Parameters
• Defines a constant with disallowed network names and max name length
• Applies constraints on network name in the builder method for setting the network name:
  • Max length of 30
  • Only alphanumeric characters or _ (because the lowercase form will be part of the cache directory path)
  • No reserved network names
• Returns the network name from testnet::Parameters instead of hard-coded values in Display trait impl for Network
• Adds an optional config field for defining the network name

Related cleanups:

• Renames ParametersBuilder::activation_heights() to with_activation_heights()
• Removes unnecessary .filter() in ParametersBuilder::with_activation_heights()

Testing

Adds a test to check that:

• It panics when setting the network name as a reserved name
• It panics when other constraints are violated (if the name is too long or disallowed characters)
• Valid network names are set and displayed
• Network is displayed correctly for Mainnet and the default Testnet

Review

Anyone can review.

Reviewer Checklist

Check before approving the PR:

• Does the PR scope match the ticket?
• Are there enough tests to make sure it works? Do the tests cover the PR motivation?
• Are all the PR blockers dealt with?
  PR blockers can be dealt with in new tickets or PRs.

And check the PR Author checklist is complete.

Follow Up Work

Add a new_regtest() constructor method to testnet::Parameters and Network (#7839)

[arya2]

@oxarbitrage Looks like rejection_restores_internal_state_genesis does sometimes fail on Windows: https://github.com/ZcashFoundation/zebra/actions/runs/8808071916/job/24176434273?pr=8411#step:12:4695

I didn't find "invalid quick check" in the logs, and check_for_duplicate_trees() returns early if there was an error, so it must be one of the detailed checks.