[MC-172449] /locate biome "finds" biomes in old world which would be different if generated newly

The bug

When upgrading an older world where the world generation was different, using /locate biome in that world might claim that it found a biome even though these chunks have already been generated in a previous version and the desired biome is therefore not there.

How to reproduce

Create a world with the following seed in any version before the 1.16 snapshots
```
5365757111184314758
```
Visit the chunks in the Nether near (0,0)
Use the version specific steps below

1.16

Open the world in a 1.16 version
Use /locatebiome in the Nether
```
/execute positioned 0 0 0 run locatebiome minecraft:soul_sand_valley
```
It claims a soul sand valley is at (0,0) even though it is not because the chunks were generated in a previous version

1.17 & 1.18-pre1

Open the world in a 1.17 or 1.18 version
Use /locatebiome in the Nether
```
/execute positioned 0 0 0 run locatebiome minecraft:crimson_forest
```
It claims a crimson forest is at (0,0) even though it is not because the chunks were generated in a previous version

1.19+

Open the world in a 1.19 version
Use /locate biome in the Nether
```
/execute positioned 0 0 0 run locate biome minecraft:crimson_forest
```
It claims a crimson forest is at (0,0) even though it is not because the chunks were generated in a previous version