--library-profiling-detail seems a bit missleading.

**Describe the bug**

It seems the flag only affects "local" packages. For "global" packages the flag is either ignored when checking if we need to rebuild or completely.

**To Reproduce**
Steps to reproduce the behavior:

```
cabal unpack hasktags
cd hasktags

# Build with library-profiling set to auto
cabal build --enable-profiling --enable-executable-profiling --enable-library-profiling --library-profiling-detail=auto

... # Builds libs +executable

# Change library profiling detail
cabal build --enable-profiling --enable-executable-profiling --enable-library-profiling --library-profiling-detail=none

```

## **Expected behavior**

I would have expected this to work similar to ghc-options where it causes packages to be rebuilt with the appropriate profiling flags set.

**System information**
- Operating system
- `cabal`, `ghc` versions

**Additional context**
Add any other context about the problem here.