chore!: do not allow contested documents for the first three epochs

[shumkov]

Issue being fixed or feature implemented

Mobile wallets aren't ready for activation date. That will enable unfair benefit for technical people who could take usernames without mobile applications. We need to delay username distribution until the point when we have both iOS and Android apps ready.

What was done?

• Reject DocumentsBatchTransition with the 10418 code if it's contained a contested document create transition.
• Allow to pass identities to the continue chain in strategy tests

How Has This Been Tested?

• Added a strategy tests where we aren't able to create a contested document on the second block but then create it successfully on 4th epoch.

Breaking Changes

State transition validation rules are changed so previously created blockchain data might not be valid.

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have added "!" to the title and described breaking changes in the corresponding section if my code contains any
• I have made corresponding changes to the documentation if needed

For repository code-owners and collaborators only

• I have assigned this pull request to a milestone

[QuantumExplorer]

We also need to add at the SDK level that it stops you from sending.

[QuantumExplorer]

Please fix clippy warnings.