image: allow autologin on TTY1 for STACKIT cloud

[burgerdev]

Context

Serial console autologin is currently not working on STACKIT, for several reasons:

• Unlike other clouds, STACKIT serial console is launched on tty1 rather than ttyS0.
• We additionally configure tty0 and ttyS1 on STACKIT, which do not exist to the best of my knowledge.
• We tried to enable serial-getty@tty0, which would have been wrong even if it were tty1 due to baud rate settings etc.

It's worth noting that systemd sets up the getty@%I.service automatically based on the console= kernel parameter, so we should only have to pass this param and configure the drop-in file for autologin.

Proposed change(s)

• Add a getty@tty1 drop-in similar to the serial-getty@ttyS0.
• Use the same console=tty1 console=ttyS0 parameters for all CSPs.
• Rename the constellation.(debug|console) parameters to constel.(debug|console) for consistency.

Additional info

• AB#4741

Checklist

• Run the E2E tests that are relevant to this PR's changes (with nightly image)
  • Azure
  • GCP
  • AWS
• Manual tests: autologin should work on console images and not on nightly images
  • Console image ref/burgerdev-console/stream/console/v2.20.0-pre.0.20241126144157-0eacf146dd07
    • GCP
    • STACKIT
    • Azure
    • AWS
  • Nightly image ref/burgerdev-console/stream/nightly/v2.20.0-pre.0.20241126144157-0eacf146dd07
    • GCP
    • STACKIT
    • Azure
    • AWS
• Add labels (e.g., for changelog category)
• Is PR title adequate for changelog?
• Link to Milestone

[netlify]

✅ Deploy Preview for constellation-docs canceled.

Name	Link
🔨 Latest commit	0eacf14
🔍 Latest deploy log	https://app.netlify.com/sites/constellation-docs/deploys/6745ecf2bd56b60008304441

[msanft]

Thanks a lot!