Add app info to exodus output

[DanielYankura]

Reason

• More info for debugging

Design

• n_processors, n_threads, and app name is now included in the input file included in the exodus output file

Impact

• adds additional data to exodus output

closes #29767

[GiudGiud]

we could just be consistent with the console and use this

std::string
outputFrameworkInformation(const MooseApp & app)

from ConsoleUtils

EDIT: now that I think about I dont want that. I m already on the fence for num processes though I dont have a strong opinion.

[moosebuild]

Job Documentation, step Docs: sync website on 37650a7 wanted to post the following:

View the site here

This comment will be updated on new commits.

[moosebuild]

Job Coverage, step Generate coverage on 37650a7 wanted to post the following:

Framework coverage

	32662f	#29786 37650a
	Total	Total	+/-	New
Rate	85.23%	85.23%	-0.00%	100.00%
Hits	108490	108493	+3	5
Misses	18794	18795	+1	0

Diff coverage report

Full coverage report

Modules coverage

Coverage did not change

Full coverage reports

Reports

• framework
• chemical_reactions
• combined
• contact
• electromagnetics
• external_petsc_solver
• fluid_properties
• fsi
• functional_expansion_tools
• geochemistry
• heat_transfer
• level_set
• misc
• navier_stokes
• optimization
• peridynamics
• phase_field
• porous_flow
• ray_tracing
• rdg
• reactor
• richards
• scalar_transport
• solid_mechanics
• solid_properties
• stochastic_tools
• thermal_hydraulics
• xfem

This comment will be updated on new commits.

[GiudGiud]

Let’s squash these two commits together

[vincentlaboure]

Thanks @DanielYankura and @GiudGiud !