[REQUEST] Add torchdynamo disable decorators to graph-break on collectives

Regarding this issue:
https://github.com/pytorch/pytorch/issues/97079

There are some comm ops in deepspeed, which for the moment aren't traceable by dynamo, and probably the best medium term solution is to make them graph-break at their entrypoint instead of failing to trace somewhere in their guts. This is accomplished by slapping a @torch._dynamo.disable marker on the ops in the deepspeed codebase (or, we can do it inside dynamo but I'm not sure that's the best approach).

Also note that there are 'traceable collectives' underway in pytorch, which ultimately could be swapped into deepspeed in order to allow tracing a graph without requiring a graph break. The proposal in this issue is more of a short-term solution to make the inevitable graph breaks happen more cleanly and predictably for users today.

Start by reviewing issue 97079 and locating the DeepSpeed collective communication operation entrypoints that are not traceable by TorchDynamo. Determine which operations need torch._dynamo.disable so they graph-break predictably, while considering the stated future replacement with traceable collectives; done means the affected operations no longer fail during tracing.