Drop moose-peacock in favor of supporting PyTorch packages

[milljm]

Motivation

There exists to many conflicts having the two made available simultaneously. Therefore it has been decided to officially begin dropping support for Peacock.

This update will likely also see a bump to Python (3.13).

Design

Begin work implementing Python 3.13 and either adding PyTorch libraries to an existing moose-* packages, or replace moose-peacock with moose-pytorch.

Impact

Peacock will effectively be unsupported. Should we remove the code from moose/python/peacock? Perhaps/Perhaps not. Or maybe discontinue the process of fighting to keep moose-peacock dependencies happy with the rest of the moose-* group (allowing a separate Conda environment to still function).

[milljm]

This PR should also close the following #28161

[lindsayad]

Is this going to conflict with #28114 ?

[milljm]

I doubt it. Part of the reason being this PR is a ways from being ready.

Plus, my conversations with @grmnptr has convinced me to not create a moose-torch package. Instead to drop moose-peacock, and allow folks to conda install pytorch -c pytorch on their own, within the moose-dev package ecosystem.

[lindsayad]

At one point in #28114 @loganharbour installed pytorch from source in moose-dev.def. That commit is still in the PR but currently reverted as we're focusing on a "clean" addition of GPU-configured mpi/petsc/mfem

[lindsayad]

We could revert the revert though in a follow-on PR if that ends up being the direction we want to go. I had troubles with the cmake files in pytorch third party libraries which is why I ended up reverting. Installing pytroch from conda would avoid the cmake configuration problems

[milljm]

New plan... Just drop moose-peacock. That will solve the more immediate issue of folks not being able to install Torch libraries.

I'll try and bump Python to 3.13 as well in this PR.