command/init: Simplify how we block upgrading the PSS provider during init -upgrade

[SarahFrench]

In #38648 the provider download process was changed:

Previously the two steps were:

1. Download providers based on configuration
2. Download providers based on state

The process remains two steps but the new steps are:

1. Download 0-1 provider if one is needed for PSS (PSS is in use)
2. Download all other providers (configuration + state)

Because the first download step is specific to the provider used for state storage we can specifically block that provider being upgraded during init. We block upgrade unless the -reconfigure flag is supplied. Users see a warning when they perform an uprgade action and PSS is in use.

Prior to this, users would get an error if the upgrade process impacted the state store provider, now it's never impacts and warnings remind users to upgrade that provider via another command.

Target Release

1.16.x

Rollback Plan

• If a change needs to be reverted, we will roll out an update to the code within 7 days.

Changes to Security Controls

Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.

CHANGELOG entry

• This change is user-facing and I added a changelog entry.
• This change is not user-facing.