Deprecate MPI_COMM_TYPE_HW_GUIDED

[GuillaumeMercier]

Problem

MPI_COMM_TYPE_RESOURCE_GUIDED achieves the same objective as
MPI_COMM_TYPE_HW_GUIDED and is more generic. There would be no need
for both, provided that MPI_COMM_TYPE_RESOURCE_GUIDED is voted in.

Proposal

Deprecate the use of MPI_COMM_TYPE_HW_GUIDED

Changes to the Text

Remove the text that defines MPI_COMM_TYPE_HW_GUIDED in MPI_Comm_split_type
as it will be eventually duplicated in the text describing MPI_COMM_TYPE_RESOURCE_GUIDED .

Impact on Implementations

None.

Impact on Users

The users would have to change a constant name in their applications.

References and Pull Requests

Complements issue #538
See also PR mpi-forum/mpi-standard/pull/650

[wesbland]

This wasn't read at the December 2022 meeting. The last opportunity for MPI 4.1 is to have it ready at the March 2022 meeting (and it needs to "pass" the reading).

@GuillaumeMercier Are you (or is someone else) planning to push this forward or should we move it out of the plan for MPI 4.1?

[jeffhammond]

I don't see any point to renaming this. The people who use this function are going to see HW and RESOURCE as the same thing.