feat(#3164): auto named abstract objects + names for horizontal anonymous objects

[maxonfjvipon]

Syntax's extended:

1. [] >> is allowed now and means that this abstract object is named automatically by the compiler. Such syntax construction can be used ONLY if the abstract object (horizontal or vertical) is used as argument of vertical application
2. x > [] > z is allowed and means the same as:

[] > z
  x > @

3. [] (a > b) > c is allowed and means the same as:

[] > c
  a > b

Closes: #3164

---

PR-Codex overview

The focus of this PR is to update various EO language files, including stdout, tuple, true, false, int, bytes, and more.

Detailed summary

• Updated methods and structures in multiple EO files
• Added new functionalities like negation, division, and conditional execution
• Updated test resources and samples for different EO language features

The following files were skipped due to too many changes: eo-parser/src/main/java/org/eolang/parser/XeEoListener.java, eo-parser/src/main/antlr4/org/eolang/parser/Eo.g4

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[yegor256]

@maxonfjvipon a much safer way would be to use the line number in the file - it is definitely unique.

[maxonfjvipon]

@yegor256 please check

[yegor256]

@rultor merge

[rultor]

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

[rultor]

@rultor merge

@yegor256 Done! FYI, the full log is here (took me 22min)