Warn about locust>=0.99

[thilp]

Explain that locust>=0.99 is not yet supported by Transformer when running a Transformer-generated locustfile in locust>=0.99.

Related to #69.

Description

Pending decision and implementation of a longer-term fix (support of v1+, potential deprecation of <0.99), we should mitigate the problem by offering clarity to our users.

Types of Changes

• Bug fix (non-breaking change which fixes an issue)

TODO

List of tasks you will do to complete the PR:

• Update the changelog.

Review

Reviewers' checklist:

• If this PR implements new flows or changes existing ones, are there
  good tests for these flows?
  If this PR rather removes flows, are the obsolete tests removed as well?
• Is the documentation still up-to-date and exhaustive? This covers both
  technical (in source files) and functional (under docs/) documentation.
• Is the changelog updated?
• Does the new version number correspond to the actual changes from this PR?
  In doubt, refer to https://semver.org.

[zincr]

🤖 zincr found 0 problems , 1 warning

ℹ️ Large Commits
✅ Approvals
✅ Specification
✅ Dependency Licensing

Details on how to resolve are provided below

---

Large Commits

Checks all commits for large additions to a single file. Large commits should be reviewed more carefully for potential copyright and licensing issues

This file contains a substantial change, please review to determine if the change comes from an external source and if there are any copyright or licensing issues to be aware of

• ℹ️ poetry.lock had +100 lines of code changed in a single commit
  Please review this file to determine the source of this change
   

[tortila]

Nice!

How funny that they actually released version 0.99 (and 0.999 too, from what I can see), right after 0.14.6

[thilp]

Yes, I think it's a trick to simulate a "redirect" from locustio to locust (not sure why 0.999 in addition to 0.99, though 😄)