The snapshot block needs to be added to the candidates set of the assumed-valid chain because it will be the tip of that chainstate right after snapshot activation.
However, adding it also to the background chainstate is not necessary for anything. Before, the index would be in the set without being connectable. It will be eventually added to the set as part of the normal block download - no extra logic is necessary here.
This simplifies a unit test which had a comment that having the block in the set is “not intended”. This was suggested here and here in #34521
Note that adding the snapshot block was harmless, since FindMostWorkChain() lazily removes blocks without data from the set, so this does not fix a bug but just simplifies some code.