ux: hide stack trace when solution exists (eg: SolverProblemError)

[abn]

An error like this can be intimidating for users. and can lead to users believing that it is a crash and not an error. We should remove the stack trace in these cases unless -vvv is used.

Updating dependencies
Resolving dependencies... (0.1s)

  SolverProblemError

  Because turicreate (6.4.1) depends on coremltools (3.3)
   and  depends on coremltools (4.0b3), turicreate is forbidden.
  So, because  depends on turicreate (6.4.1), version solving failed.

  at ~/.poetry/lib/poetry/puzzle/solver.py:241 in _solve
      237│             packages = result.packages
      238│         except OverrideNeeded as e:
      239│             return self.solve_in_compatibility_mode(e.overrides, use_latest=use_latest)
      240│         except SolveFailure as e:
    → 241│             raise SolverProblemError(e)
      242│
      243│         results = dict(
      244│             depth_first_search(
      245│                 PackageNode(self._package, packages), aggregate_package_nodes

Example sourced from #3011

[lowitea]

Hi!
I have made a PR #3111
@abn could you please review it

[mpernigo]

Hey! I was just starting to look into this. Let me know if I can help

[Secrus]

Stack traces are now hidden by default

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.