It would be nice to be able to disable particular chroot in every project
if the chroot goes EOL, but still let the interested people re-enable the
chroots if they absolutely have to. Then, after certain time period,
we could hit the "full EOL" as we know it now.

When the chroot goes "soft EOL", the chroot contents will be marked
for removal after certain period of time (likely 180 as usually). So users
can prolong the chroots as usual. It's important to do this, otherwise
we don't cleanup the storage on backend soon enough.

Technical detail: We have to fix the models so "chroot disable" action
in copr project means just "delete_after = timestamp" and "disabled=True".
This will allow us to implement any such awesome logic almost for free.