Move confidence threshold out of /dataset_info

[JosephMarinier]

Description:

The idea is to remove pipeline-specific info from /dataset_info.

• Fix typo in breadcrumbs
• Clean up
• Move confidence threshold out of /dataset_info and into /bins and /utterances
  • I tried two approaches to get some feedback:
    • For /utterances, I get the confidence threshold in the router.
    • For /bins, I get the confidence threshold in the module. I have some trouble with pipeline_index. Before investing more time, is that even a sensible approach?

Checklist:

You should check all boxes before the PR is ready. If a box does not apply, check it to acknowledge
it.

• PRE-COMMIT. You ran pre-commit on all commits, or else, you
  ran pre-commit run --all-files at the end.
• FRONTEND TYPES. Regenerate the front-ent types if you played with types and routes.
  Run cd webapp && yarn types while the back-end is running.
• USER CHANGES. The changes are added to CHANGELOG.md and the documentation, if they impact
  our users.
• DEV CHANGES.
  • Update the documentation if this PR changes how to develop/launch on the app.
  • Update the README files and our wiki for any big design decisions, if relevant.
  • Add unit tests, docstrings, typing and comments for complex sections.

[Dref360]

LGTM

[JosephMarinier]

@Dref360, could you advise on the "two approaches" I mentioned in the PR description? Are both OK?

• I tried two approaches to get some feedback:
  - For /utterances, I get the confidence threshold in the router.
  - For /bins, I get the confidence threshold in the module. I have some trouble with pipeline_index. Before investing more time, is that even a sensible approach?

[Dref360]

Yeah, to me it makes sense to return the threshold in a router OR in a Module depending on the usecase. The way you did it is great!

[gabegma]

Can we merge this?