[RFC] Different menaning of angle parameter in affine and rotate ops

In Torchvision stable API, there are 2 ops: affine and rotate that has angle as parameter.

However, positive angle parameter in F.affine op performs clockwise rotation.

https://github.com/pytorch/vision/blob/8aadef5f55a8a0098de943dbf0480a796022e825/torchvision/transforms/functional.py#L1092

while in F.rotate it is an opposite meaning, it does counter clockwise rotation:

https://github.com/pytorch/vision/blob/8aadef5f55a8a0098de943dbf0480a796022e825/torchvision/transforms/functional.py#L1004

For Detectron2, Pillow or albumentations, they do counter clockwise rotation for positive angle value.

Question: Should we align F.affine op to perform counter clockwise rotation for positive angle value ?

cc @vfdev-5 @datumbox

Compare the affine and rotate implementations in torchvision/transforms/functional.py at the linked locations, then review how the angle convention is described for each operation. Check the cited Detectron2, Pillow, and albumentations conventions before proposing an API decision. Done means the convention is agreed and the affected documentation, tests, and behavior changes are identified.