Remove outdated v1 to v2 upgrade guide from README.md

Author: jdreesen

README.md

@@ -32,33 +32,6 @@ It can be useful for testing purposes or for seeding a database with initial dat
          resource: '../tests/Fixture/'
    ```
 
-### Upgrading From an Earlier Version
-
-Fixtures are now considered actual services and are loaded through Dependency Injection (DI).
-To align with this approach,
-you’ll need to update your Fixture classes by moving service dependencies from the `create` method to the constructor.
-If your Fixture relies on other Fixtures, implement the `HasDependencies` interface.
-
-Here are the key changes:
-
-1. **Fixture Interface Update**  
-   The old fixture interface `Neusta\Pimcore\FixtureBundle\Fixture` has been replaced with `Neusta\Pimcore\FixtureBundle\Fixture\Fixture`. 
-   You can also extend from `Neusta\Pimcore\FixtureBundle\Fixture\AbstractFixture` to implement your Fixtures.
-
-2. **Fixtures as Services**  
-   Fixtures must be made available in the Dependency Injection container to be discovered. 
-   To do this, tag them with `neusta_pimcore_fixture.fixture`, or use autoconfiguration for automatic tagging.
-
-3. **Change of the `create` Method**  
-   The signature of the `create` method has been modified. 
-   It no longer takes any arguments, meaning all dependencies must be specified via `HasDependencies`.
-
-4. **Specifying Inter-Fixture Dependencies**  
-   If your Fixture depends on others, use the `HasDependencies` interface to specify these dependencies. 
-   Additional guidance is available in the section "[Referencing Fixtures and Depending on Other Fixtures](#referencing-fixtures-and-depending-on-other-fixtures)".
-
-Make sure to update your Fixture classes according to these changes to ensure proper functionality and compatibility with this Bundle.
-
 ## Usage
 
 ### Writing Fixtures