TUI | Follow-up from textual updates

• Check if we can and should use new :odd / :even TCSS pseudoselectors (e.g. to replace CLIVE_ODD_COLUMN_CLASS_NAME) (https://github.com/Textualize/textual/releases/tag/v0.84.0)
• Check if we can and should use new :first-of-type, :last-of-type TCSS pseudoselectors (https://github.com/Textualize/textual/releases/tag/v0.84.0)
  • it looks like there should be places that can use that, however, it can be hard to determine and refactor all the places
• Check if we can and should use new background-tint TCSS rule (https://github.com/Textualize/textual/releases/tag/v0.84.0)
  • it looks like there are places that could use that. Look for rgba/rgb.
• Check if we can and should replace Button.Pressed with action param (https://github.com/Textualize/textual/releases/tag/v0.85.0)
  • it looks like it's better not to combine key binding action and button action into a single method
• Check if we can and should use the HorizontalGroup/VerticalGroup (https://github.com/Textualize/textual/releases/tag/v0.85.0)
  • looks like there should be places that could benefit from that.
• Check if we can and should use the Select.selection instead of Select.value (e.g. in CliveSelect) (https://github.com/Textualize/textual/releases/tag/v0.87.0)
  • looks like not, because the current Textual implementation could raise assertion while is typhinted to return None
• Check if we can and should use border: tab TCSS rule (https://github.com/Textualize/textual/releases/tag/v0.89.0)
• Check if we can and should use text-overflow (and maybe text-wrap) TCSS rules (https://github.com/Textualize/textual/releases/tag/v2.0.0)
• Check if we can and should use text-padding TCSS rule (https://github.com/Textualize/textual/releases/tag/v3.0.0)
• Check if we can and should use :first-child and :last-child pseudoclasses (https://github.com/Textualize/textual/releases/tag/v3.2.0)
• Check if we can and should use toggle_class of reactive (https://github.com/Textualize/textual/releases/tag/v3.2.0)
• Check if we can and should use compact instead of e.g. OneLineButton (https://github.com/Textualize/textual/releases/tag/v3.2.0)
• Use textual-speedups when becomes production ready (https://github.com/Textualize/textual/releases/tag/v3.4.0)
• Content markup is now more lenient, looks like we don't need the markup=false workaround anymore (https://github.com/Textualize/textual/releases/tag/v3.4.0)):
  • check 115c89e5 and cff7f3d6 and 3d17feca
• Check if we can use textualgetters (https://github.com/Textualize/textual/releases/tag/v3.7.0)
  • looks like we can replace them with @property thas does a query but looks like there is no getter yet for more safer query_exactly_one
• Check if we can and should use new :empty TCSS pseudoselector (https://github.com/Textualize/textual/releases/tag/v5.1.0)
• Check if we can and should use new Screen.action_focus (https://github.com/Textualize/textual/releases/tag/v5.1.0)
  • looks like can be used in BINDINGS
• Check if we can and should use new reactive.Initialize (https://github.com/Textualize/textual/releases/tag/v5.3.0)
  • looks like in some cases we refer to default factory function defined outside of the class like local_profile: Profile = var(get_default_profile, init=False)
• Check if we can and should use new Binding.Group (https://github.com/Textualize/textual/releases/tag/v6.0.0)
• Check if we can and should use new Button.flat (https://github.com/Textualize/textual/releases/tag/v6.1.0)