Importing an image as a Texture2DArray does not change the suffix to .tres and you cannot use it in a Texture2DArray node in visual shader

### Tested versions

Reproducible in godot 4.2.1 stable mono

### System information

Godot v4.2.1.stable.mono - Windows 10.0.22621 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3050 Laptop GPU (NVIDIA; 31.0.15.3699) - AMD Ryzen 7 4800H with Radeon Graphics (16 Threads)

### Issue description

I have texture2d files in godot, visible in the file manager.

I reimport one as a texture2dArray.

If I mouseover the file, godot now says it is a texture2dArray.

But the file suffix remains unchanged.. eg it stays as .jpg or .png or whatever.

If I look at the file in the inspector, it allows me to step through the slices, so it really is a texture array. However, it is NOT a .tres file

Because it is not a .tres file, I cannot drag it onto a Texture2dArray node in the visual shader editor.

### Steps to reproduce

1. Reimport a file as a texture2Darray
2.. Mouseover it in the file window at bottom left of godot. Notice godot now says it is a Texture2Darray.
3. Create a visual shader, then edit it and select fragment node
4. Create a texture2dArray node
5. Try to drag your newly created texture2dArray onto the node..you cannot .
6. try to LOAD your newly created texture2dArray into the node....you cannot . Load will only accept files ending in .tres and the texture2Darray still has the original file suffix

### Minimal reproduction project (MRP)

n/a

Reproduce the issue by reimporting an image as a Texture2DArray, then using the visual shader editor's Texture2DArray node and its load action. Inspect how the imported resource is represented after reimport and how the node filters files. Done means the imported Texture2DArray can be dragged onto or loaded into the node.

Written by the indexing model from the issue text.