STYLE use force-grid-wrap in isort

[MarcoGorelli]

• Ensure all linting tests pass, see here for how to run them

As discussed in the monthly dev meeting - motivation here is to reduce the number of merge conflicts, which single-line imports seem to be a major source of.

some examples of such conflicts (which force_grid_wrap would avoid):

#37467 :

<<<<<<< GH37278
from typing import TYPE_CHECKING, Optional
=======
from __future__ import annotations

from typing import TYPE_CHECKING
>>>>>>> master

#34426 :

<<<<<<< 8745-from_dummies
from typing import TYPE_CHECKING, Any, Dict, Hashable, List, Optional, Type, Union, cast
=======
from typing import (
    TYPE_CHECKING,
    Dict,
    Hashable,
    List,
    Optional,
    Sequence,
    Type,
    TypeVar,
    Union,
    cast,
)
>>>>>>> master

#29944 :

<<<<<<< subplot_groups
from collections import Counter, Iterable
from typing import TYPE_CHECKING, Hashable, List, Optional, Sequence, Tuple, Union
=======
from __future__ import annotations

from typing import TYPE_CHECKING, Hashable, List, Optional, Tuple
>>>>>>> master

---

This changes a huge number of files in one go, but all I've done is

git reset --hard upstream/master
# add `force_grid_wrap` option to setup.cfg
pre-commit run isort -a
git commit -m 'force grid-wrap' -a

[jreback]

i think this is fine. please merge master and ping when green so can merge.

[jreback]

thanks @MarcoGorelli