Improving cabal haddock UX

I think that it is currently very cumbersome to look up the documentation of packages locally. The biggest problem is that it is rather hard to find the documentation files of dependencies.

The current situation is that running `cabal haddock` on a local project shows the path to the documentation index of that project after compiling. However, it does not show the path to the documentation of dependencies and does also not show the path if nothing needs to be compiled.

Discovering local haddock documentation would be much simpler if:
1. `cabal haddock` would always show the path to the documentation of the project, regardless if compilation was necessary or not.
2. `cabal haddock text` would show the path for the `text` documentation.

Additionally, it would be nice if cabal had a flag to automatically open the documentation after compiling. For example, `cabal haddock text --open` should open the documentation for `text`.

The `--open` functionality seems to have been implemented in https://github.com/haskell/cabal/issues/7366, but current cabal(3.6.2.0) does not have this functionality.

What do you think about my suggestions?