Cabal should warn about `-fprof-late` being passed as ghc flags when the default profiling detail is used.

It seems to be a common mistake for people trying to use late cost centres to pass `-fprof-late` as a ghc flag without setting the profiling detail. This is pretty much always a mistake as those flags don't work well together resulting in more overhead without producing a better profile.

Here is such an instance: https://github.com/well-typed/optics/issues/469

**Expected behavior**

It would be great if cabal would warn if `-fprof-late` is passed as a ghc flag without `profiling-detail` having been explicitly set. Similar to what it already does for `-prof`.