[DOCS] Finding Classification Mistakes Tutorial, needs more verbose ending

[cupcakesprinkle3]

URL(s) with the issue

https://docs.voxel51.com/tutorials/classification_mistakes.html

Description of proposal (what needs changing)

First, the current tutorial ends with this: "FiftyOne currently offers integrations for both Labelbox and Scale."

However, there are now many more integrations with annotation tools! I would suggest making it clear that FiftyOne integrates with many popular annotation tools, and list a longer sampling, and/or link to a "landing page" where all the annotation integrations are listed in one place.

Second, the current tutorial, in the first sentence of the last paragraph just before mentioning the integrations is missing the notion of how easy it is to tag something in FO and automatically send it to an annotation of choice once an integration and/or plugin is involved.

Current text: In a real world scenario, we would then take the ground truth classifications that are likely mistakes and send them off to our annotation provider of choice as annotations to be reviewed.

Possible future text: In a real world scenario, we would want to send the likely mistakes to an annotation tool or vendor to be reviewed and corrected. Did you know you can automate this workflow? Use one of FiftyOne's annotation integrations to review and correct annotation mistakes quickly and seamlessly.

Willingness to contribute

The FiftyOne Community encourages documentation contributions. Would you or another member of your organization be willing to contribute a fix for this documentation issue to the FiftyOne codebase?

• Yes. I can contribute a documentation fix independently
• Yes. I would be willing to contribute a documentation fix with guidance from the FiftyOne community
• No. I cannot contribute a documentation fix at this time