Visual Shaders: Make output-ports for vector types expandable by default

[DennisManaa]

This PR is a continuation of the work done in: #73041

Changes made

On the left side you can see the state before the changes I made (which is the same as in #73041) and on the right side you can see the state after the changes I made. The following changes were made:

• Marked in red: Removed the expand buttons from the vector-components.
• Marked in blue: Renamed the component-ports, to better reflect which vector-component is meant (as suggested by @Norrox).
• Marked in yellow: Reversed the directions of the collapse/expand-arrows when open/closed, which aligns them with other occurrences of these buttons.
• Marked in magenta: Fixed outputs of Vector2Parameter, Vector3Parameter, Vector4Parameter and CurveXYZTexture-Nodes.
• Marked in cyan: Fixed many nodes that weren't working correctly (the preview and output of vector-components were interpreted as if they were vector-outputs, what caused ports of several nodes to behave strangely)

[Chaosus]

Thanks, this PR looks very good. Please squash commits as required by our pipeline (see https://docs.godotengine.org/en/latest/contributing/workflow/pr_workflow.html#making-changes)

[QbieShay]

PR looks good to me, my only comment on this is that I find the red(x) syntax very hard to read. I'd rather we remove this change and discuss a bit wheter we want to have some nodes be rgba and some nodes directly xyzw, or find some less visually cluttered ways to represent this.

[Norrox]

PR looks good to me, my only comment on this is that I find the red(x) syntax very hard to read. I'd rather we remove this change and discuss a bit wheter we want to have some nodes be rgba and some nodes directly xyzw, or find some less visually cluttered ways to represent this.

I like this PR 😁, would it be better to remove red green blue text completely and for example just write X in color red and the port be red as it is?

[AThousandShips]

example just write X in color red and the port be red as it is

That's not appropriate for accessibility, neither from a visibility perspective or from the perspective of communicating information without relying on color

[QbieShay]

I'd rather get this pr merged soon and discuss on those UI changes separately, possibly in a proposal

[DennisManaa]

Thank you very much for your rapid feedback. I'm glad to hear that you like this PR :)
I squashed the commits and reverted the changes regarding the naming of the ports.

For the future, it might be a good idea to consider changing the naming of the vector components in a way that will allow for different names for different nodes. One way to implement this would be to create a new virtual function in the VisualShaderNode class and override this function where needed. This approach would enable us to use appropriate names for every node, such as 'u' and 'v' for nodes that output UVs.

[DennisManaa]

Sorry for this change...

I just realized I made a mistake in the commit message. The 'Co-authored-by:' tag wasn't recognized correctly, so I've corrected it. I built on top of QbieShay's work, so it should correctly be represented in the commit! :)

[akien-mga]

Thanks! And congrats for your first merged Godot contribution 🎉