(breaking change) Remove support of GO Feature Flag v0.x.x flag format

[thomaspoignant]

Context

In version v1.0.0 GO Feature Flag has dropped the legacy format of the flag of the v0.0.0 in order to move to a multi-variations format that has enable new features for GO Feature Flag.

To avoid any breaking changes we have kept the compatibility with the v0.x.x and continue to support it.

The last release of version v0.x.x was 12 December 2022 (v0.28.2) and since then we have released more than 34 versions of GO Feature Flag v1.x.x it is now time to clean the code and remove any trace of the v0.x.x format.

In this issue we will link all the associated issues of this project to be able to track the progress of this initiative.

You are still using the legacy format?

If you are still using the legacy format you can easily convert your file containing GO Feature Flag flags with the migration cli.

How to do that? Just follow the instruction in our documentation.

List of issues to complete to consider this one done

All those issues have to be executed in the order of this list.

1. Log error when v0.x.x flag format is used #2399
2. Stop releasing migration cli #2400
3. Change all tests using v0.x.x flag format #2401
4. Remove migration cli code #2402
5. Refactor DTO layer to support v1 flag format only #2403

[thomaspoignant]

/assign-me

[github-actions]

👋 Hey @thomaspoignant, thanks for your interest in this issue! 🎉

⚠ Note that this issue will become unassigned if it isn't closed within 10 days.

🔧 A maintainer can also add the 📌 Pinned label to prevent it from being unassigned automatically.