Extracts CandidateDetail component from MlCandidateShow

What does this MR do and why?

The candidate detail table is going to be used to display a model version candidate in the Model registry. To be able to reuse the code, we are first extracting the detail table into its own component under the model registry folder (since eventually all model experiment code will be part of the model registry)

This MR does not change anything UX wise, it only refactors the components.

How to set up and validate locally

1. Create the data (in rails console):

   project_id = 1 # whatever project you want to use for testing
   p = Project.find_by(id: project_id) 
   e = Ml::Experiment.create!(project: p, name: "GitLab experiment")
   c = e.candidates.create(project: p)
   c.metrics.create(name: "AUC", value: 0.1, step: 0)
   c.metrics.create(name: "Accuracy", value: 0.2, step: 2)
   c.metrics.create(name: "Accuracy", value: 0.5, step: 3)
   c.metadata.create(name: "some name", value: "some data")
   c.params.create(name: "max-depth", value: "3")

2. Navigate to your project, then Analyze > Model experiments. Select the experiment and then the candidate

3. Verify that nothing changes visually when the code changes are applied

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

Related to #428905 (closed)