Fly Console should always allocate pty

[swilson-fly]

Change Summary

What and Why:
In #4703 fly console was updated to more closely match fly ssh console in behaviour. This changed how it allocated ptys for the connection, making it so it wouldn't allocate it if a command is specified.

However fly console uses the console_command config in the toml, as it's command even if a -c isn't specified so this is always true. This meant that it always stopped allocating ptys, breaking the main functionality of fly console. This command is almost always used for opening a rails console for debugging, so it's always interactive.

This reverts the change from 4703 back to it's original, always interactive behaviour. As an alternative we could split out console_command vs --console, but since this allocates a whole new machine using it for a non-interactive, one off result seems too heavy. For one offs users should probably use fly ssh console --command

How:

Reverts console behaviour back to always allocating a pty.

Related to:

PR 4703 cc: @mattp-fly

---

Documentation

• Fresh Produce
• In superfly/docs, or asked for help from docs team
• n/a

[swilson-fly]

Failing check is due to an unrelated issue: aborted: machine is replacing: concurrent update in progress