Deprecate gp timeout extend and review timeout defaults

[loujaybee]

With the introduction of gp timeout set, and usage based pricing, the gp timeout extend behaves in unexpected and unpredictable ways. When you set a new timeout to, let's say 15 hours, running gp timeout extend now arbitrarily reverts the timeout back to 3 hours. Soft deprecate gp timeout extend (e.g. remove from documentation and CLI to protect backwards compatibility) and instruct users to use gp timeout set 180m as an alternative.

[Siddhant-K-code]

💭 Deprecate gp timeout extend would be more ideal to have less & specific options. We also need to handle these:

• Command Palette:
  

• Bottom Status Bar:
  

[mbrevoort]

Do we know how often extend is used?

Alternatively, even if we do decide to deprecate, we should at least make extend never reduce the time out. If it's less than three hours, then set it to three hours. If it's more than three hours, then do not update its value.

[Siddhant-K-code]

Do we know how often extend is used?

Not much. Usage is ~85 times a week.

If it's less than three hours, then set it to three hours. If it's more than three hours, then do not update its value.

💯 That sounds like a good first step. 🙋‍♂️

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Siddhant-K-code]

It is already implemented now -- feature docs