Rename featureStatus used for annotations

[nmittler]

The use of featureStatus as a field in the annotations is incorrect and confusing. It's not really a status of the feature, but rather the status of that one API which configures some part of a larger feature. Perhaps just simply status would be more clear?

[ ] Configuration Infrastructure [x] Docs [ ] Installation [ ] Networking [ ] Performance and Scalability [ ] Policies and Telemetry [ ] Security [ ] Test and Release [ ] User Experience

Expected behavior

Steps to reproduce the bug

Version (include the output of istioctl version --remote and kubectl version)

How was Istio installed?

Environment where bug was observed (cloud vendor, OS, etc)

[nmittler]

FYI @therealmitchconnors @jasonwzm

[istio-policy-bot]

🚧 This issue or pull request has been closed due to not having had activity from an Istio team member since 2021-01-06. If you feel this issue or pull request deserves attention, please reopen the issue. Please see this wiki page for more information. Thank you for your contributions.

Created by the issue and PR lifecycle manager.