### Godot version

v4.2.stable.official [46dc27791]

### System information

Godot v4.2.stable - Windows 10.0.19045 - Vulkan (Forward+) - integrated Intel(R) HD Graphics 630 (Intel Corporation; 31.0.101.2111) - Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz (4 Threads)

### Issue description

I have a tileset that disables its visibility during it's `_ready()` function. The tileset is made up of scene tiles. I didn't have a problem with this until recently I discovered my player goes right through the tiles unless they're visible. This didn't happen before, it could be something to do with the 4.2 update.

### Steps to reproduce

In my minimal reproduction project I removed the script that disables the tileset's visibility.

- Run the game with the tileset visible and use wasd keys to move downward. The tileset should block the player (it's using `move_and_slide()`).
- Run the game with the tileset non-visible and use wasd keys to move downward. The tileset isn't block the player.

### Minimal reproduction project

[Bug Demo.zip](https://github.com/godotengine/godot/files/13531278/Bug.Demo.zip)

PackedStringArray warnings = Node::get_configuration_warnings();
	
	RBSet<int> y_sorted_z_index;
	for (const Ref<TileMapLayer> &layer : layers) {
		if (layer->is_y_sort_enabled()) {
			y_sorted_z_index.insert(layer->get_z_index());
		}
	}
	
	for (const Ref<TileMapLayer> &layer : layers) {
		if (!layer->is_y_sort_enabled() && y_sorted_z_index.has(layer->get_z_index())) {
			warnings.push_back(RTR("A Y-sorted layer has the same Z-index value as a not Y-sorted layer.\nThis may lead to unwanted behaviors, as a layer that is not Y-sorted will be Y-sorted as a whole with tiles from Y-sorted layers."));
			break;
		}
	}
	if (!is_y_sort_enabled()) {
		
		for (const Ref<TileMapLayer> &layer : layers) {
			if (layer->is_y_sort_enabled()) {
				warnings.push_back(RTR("A TileMap layer is set as Y-sorted, but Y-sort is not enabled on the TileMap node itself."));
				break;
			}
		}
	} else {