Fixed writing multiple StripOffsets to TIFF

[Yay295]

The StripOffsets values don't really mean anything without associated image data, so I just did the same thing as when this tag only has one value and added the IFD offset to the values.

StripOffsets is overwritten with correct values when writing TIFF images, so this only matters when writing a non-TIFF image, where StripOffsets doesn't mean anything. The main benefit of this change is that it won't raise an exception now when saving a non-TIFF image with EXIF data copied from a TIFF image that has more than one strip.

[radarhere]

Suggested change

	values = [val + offset for val in handler(self, data, self.legacy_api)]
	values = [val + offset for val in handler(self, data)]

Throwing this suggestion out there, see what happens - considering that this should be SHORT or LONG (or LONG8), it doesn't matter whether the legacy API is in use or not, as they're all passed to

Pillow/src/PIL/TiffImagePlugin.py

Lines 502 to 505 in b557876

	def basic_handler(
	self: ImageFileDirectory_v2, data: bytes, legacy_api: bool = True
	) -> tuple[Any, ...]:
	return self._unpack(f"{len(data) // size}{fmt}", data)

[Yay295]

I think it's more correct to pass the value since we have it. The value not being used is an implementation detail that this call shouldn't be concerned with.

[radarhere]

StripOffsets is overwritten with correct values when writing TIFF images

If libtiff is used when saving, yes. Otherwise, no.