SNESGetSNESLineSearch: use auto Fortran binding
SNESGetLineSearch / SNESSetLineSearch: rename for consistency

This function was introduced as SNESGetPetscLineSearch, which matches no
established convention, then changed to SNESGetSNESLineSearch according
to the object name SNESLineSearch.  This is inconsistent with names such
as MatGetInfo, MatGetColoring, MatGetNullSpace, MatGetLocalToGlobalMapping,
SNESGetConvergedReason, and TSGetAdapt.

This is a change from petsc-3.3.
Merge branch 'jed/snesgetlinesearch' into next

* jed/snesgetlinesearch:
  SNESGetLineSearch / SNESSetLineSearch: rename for consistency
  SNESGetSNESLineSearch: use auto Fortran binding
SNESGetSNESLineSearch / SNESSetSNESLineSearch: mark as deprecated (C interface only)
Merge branch 'jed/snesgetlinesearch' into next

* jed/snesgetlinesearch:
  SNESGetSNESLineSearch / SNESSetSNESLineSearch: mark as deprecated (C interface only)
PCView: warn about incomplete information before PCSetUp
PCView_MG: avoid SEGV before PCSetUp
Merge branch 'jed/pcview-before-setup' into next

* jed/pcview-before-setup:
  PCView_MG: avoid SEGV before PCSetUp
  PCView: warn about incomplete information before PCSetUp
Merge branch 'madams/gamg-mem'

* madams/gamg-mem:
  PCGAMG: add PCGAMGInitializePackage (fixes memory leak)
Viewer: add PETSCVIEWERVTK for Fortran
Merge branch 'master' into next

* master:
  Viewer: add PETSCVIEWERVTK for Fortran
PetscViewer: Added VTK type for Fortran
DMPlex: Tutorial now shows how to output VTK
Merge branch 'knepley/plex' into next

* knepley/plex:
  DMPlex: Tutorial now shows how to output VTK
  PetscViewer: Added VTK type for Fortran
mat-ex125: fix syntax with 'case' and preprocesor.
Subject: Re: [petsc-maint] [petsc-maint #160633] RE: [petsc-users] ksp for AX=B system
Merge branch 'balay/fix-ex125' into next
petscsys: conditional define of {MPICH,OMPI}_SKIP_MPICXX
Merge branch 'maint'

* maint:
  petscsys: conditional define of {MPICH,OMPI}_SKIP_MPICXX

Conflicts:
	include/petscsys.h ("mpi.h" to <mpi.h>)
TS ex11: set field names and number of components
DMPlex: teach VTU output about field names and components

Schema is "${ObjectName}${FieldName}.${Component}".  For example

  SolutionDensity.0
  SolutionMomentum.0
  SolutionMomentum.1
  SolutionMomentum.2
  SolutionEnergy.0