Raster layers crossing antimeridian are incorrectly transformed on non-mercator projections

Nobody has claimed this yet.

**mapbox-gl-js version**: 3216f1ce2ed8acabb661caa498d6068acf5ec0b9 and v2.6.0-beta.1

**browser**: google chrome 95.0.4638.54, safari 15.1, firefox 93

### Steps to Trigger Behavior

1. Enable any non-mercator projection
2. Add raster layer, e.g. [this time zone chart of the world in mercator](https://tile.loc.gov/image-services/iiif/service:gdc:gdcwdl:wd:l_:06:77:6:wdl_06776:am007837/full/pct:25/0/default.jpg) (note that is's crossing antimeridian)

```js
map.addLayer({
'id': 'mercator',
'type': 'raster',
'source': {
type: 'image',
url: 'https://tile.loc.gov/image-services/iiif/service:gdc:gdcwdl:wd:l_:06:77:6:wdl_06776:am007837/full/pct:25/0/default.jpg',
coordinates: [
[-257, 81.3],
[175, 81.3],
[175, -74],
[-257, -74]
]
},
paint: {
'raster-opacity': 0.2,
}
});
```

### Link to Demonstration

https://jsbin.com/metanol/edit?js,output

### Expected Behavior

The image is transformed on the map according to the coordinates.

#### Mercator

### Actual Behavior

The image is not transformed as with Mercator projection

#### Equal Earth

#### Equirectangular

#### Albers

#### Lambert Conformal Conic

https://user-images.githubusercontent.com/533564/140303679-2b7c1f09-1ca8-41b4-831b-b9b79eecc792.mov

Reproduce the issue with the linked JSBin example, using the supplied raster image and non-mercator projections. Trace how raster layers crossing the antimeridian are transformed, then verify that the image follows its coordinates consistently across the affected projections.

Written by the indexing model from the issue text.