[GSK-1408] Fix console errors on frontend

[henchaves]

Description

This PR aims to solve a lot of "console error" logs. The idea is to make everything working really well to migrate the frontend from Vue 2 to Vue 3 smoothly.
It modifies many files, so I apologise for the huge amount of code to review without being related to each other.

Related Issue

GSK-1408 (available on Linear)

Type of Change

• 📚 Examples / docs / tutorials / dependencies update
• 🔧 Bug fix (non-breaking change which fixes an issue)
• 🥂 Improvement (non-breaking change which improves an existing feature)
• 🚀 New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to change)
• 🔐 Security fix

[linear]

GSK-1408 Fix console errors on frontend

1. Migrate PredictionExplanations.vue to Composition API

2. Interact with UI tabs (e.g. Debugger, Testing) and look for console errors (developer tools)

3. Interact with paid license and look for console errors

4. Solve these errors

[kevinmessiaen]

I'm not a big fan of catching error and silencing them. Apparently a solution to update query params on the same route is to push the params only, but we will need to check if the route is the same or not each time...

await router.push({
    params: {
      projectId: props.projectId.toString()
    }
  })

[henchaves]

I implemented this logic of checking if the route is the same or not, and it keeps displaying the Navigation error if I remove the catch statement

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

0.0% Coverage
0.0% Duplication