Manual fixes needed for linter for the KSP directory

Profiling: Improve !defined(PETSC_USE_LOG) #defines

- If we cast macro arguments to void, we can avoid unused errors that have
forced lots of conditionally included code like this:

```c
#if def

Profiling: Improve !defined(PETSC_USE_LOG) #defines

- If we cast macro arguments to void, we can avoid unused errors that have
forced lots of conditionally included code like this:

```c
#if defined(PETSC_USE_LOG)
PetscLogEvent event;
#endif
```

- Having global counters like petsc_TotalFlops externed event
if !PetscDefined(USE_LOG) helps to remove a lot of needless
`#ifdef`s around code that can instead be placed in
`if (PetscDefined(USE_LOG)) {}` blocks.

show more ...

Track levels of nesting of KSP, for example KSPBJACOBI has nesting 1 higher than the calling KSP

... and apply it

Rename PetscValidPointer -> PetscAssertPointer

Deploy new PetscValidPointer, remove PetscValidXXXPointer

Lint apply: ksp

HAVE_FORTRAN should be USE_FORTRAN_BINDINGS since it is about generating the Fortran bindings, not about if the Fortran compiler exists

PCMG: in principle any failure should trigger the setup error