Rename `retryable?` in presenter to frontend specific name.

The following discussion from !52463 (merged) should be addressed:

• @allison.browne started a discussion: (+1 comment)

  non-blocking: It would probably break the contract with the front end but I wonder if this deserves a separate name from the model logic since it controls whether the manual retry button is available and is different logic than wheather the pipeline can be auto retried. maybe: retry_available? or retry_button_available?

As part of this issue we should also address !116408 (comment 1360580948)