Add note about cirq-ft status on PyPI and suggest alternatives

[ArisAthena]

Changes - Added a note in the README.rst file about cirq-ft being no longer maintained. - Suggested Qualtran as an alternative.

Related Issue Addresses #6862

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.85%. Comparing base (0d9a6ee) to head (59aa477).
Report is 43 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6868      +/-   ##
==========================================
- Coverage   97.86%   97.85%   -0.01%     
==========================================
  Files        1084     1084              
  Lines       94013    94013              
==========================================
- Hits        92004    91999       -5     
- Misses       2009     2014       +5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[mhucka]

Thank you for trying this. Unfortunately, the issue in question is the description on PyPI, not in GitHub, and so it cannot be addressed with changes to this particular README file.

I regret to say that this PR is just not applicable. @ArisAthena would you mind closing this PR?

[dstrain115]

Want to add a link? Otherwise, LGTM.

[mhucka]

@dstrain115 I don't think putting this info in the Cirq readme will be all that useful, plus the Cirq README is about to change. I think we should close the PR, since the OP has not responded for 2 weeks.

[dstrain115]

Closed since this is not the right place to put these changes.