Godot 3 to 4 Conversion: scene Label align and valign values get discarded

[Reneator]

Godot version

v4.0.stable.official [92bee43]

System information

Windows 10

Issue description

Label align and valign just get discarded, having to replace them with the new values.
in the .tscn files it would be a conversion of:

valign = 1 = vertical_alignment = 1
align = 1 = horizontal_alignment = 1

~~
But to get it to actually work the Label inside the tscn would also need to get the layout_mode = 2 attribute to have set, else it will discard the replaced values~~
(After specific testing this doesnt seem to be the culprit, but the main issue above still stands)

(Tested by changes via external text-editor on the tscn file directly before opening it.)

Steps to reproduce

migration from 3.X to 4

Minimal reproduction project

Reproduction label center getting lost.zip

[YuriSizov]

Layout mode has nothing to do with text alignment inside of the label. You do have a typo in your code sample though.

[Reneator]

Fixed the typo, that happens if you do it free hand.

Its just a behaviour that i noticed, that if i just replace the align and valign with the new property names, those settings get discarded, unless i also add the layout_mode = 2 in the .tscn

[YuriSizov]

That's not possible, something else must be happening at the same time. Please provide MRP that demonstrates the issue.

[Reneator]

Added an MRP created in godot v3.5.1.stable.official [6fed1ff] with 3 .tscn files, 3 times just a label with centered text, the first one with no manual changes to the .tscn,
the second with the new names for the align and valign and the third with the layout_mode = 2 also added.

(The third one is not relevant for the core issue of this topic, but just wanted to leave it in for test-purposes)

The first scene will remove the alignment
the second scene will keep the alignment due to proper renaming, done manually.

[naturally-intelligent]

Also had this issue, had to reset all labels by hand

[Quimisagi]

Tried this on my machine using the MRP and can confirm that the issue exists. Will try to fix it.