Marking old CuPy 13 packages (with activation scripts) broken

[jakirkham]

After discussion in issue ( #206 ), we decided recently to drop the activation scripts from CuPy packages ( #252 ). This happened in CuPy 13 packages, but only started with build/number: 3. As this is a breaking change and it happened in a later build/number, some CuPy 13 packages have activation scripts and others do not. To make the user experience more consistent, it would be preferable for CuPy 13 packages that had activation scripts to be marked broken. This way the breaking change of removing activation scripts aligns to installing CuPy 13 (a major version that can contain other breaking change)

Note: This is a follow up to comment ( #206 (comment) ) and offline discussion with @leofang and @mtjrider where we thought this would be a reasonable change

[jakirkham]

If this is reasonable, the next steps would be:

• Identify the CuPy packages before the change
• Compile a list of them
• Follow these steps to mark the packages broken

[leofang]

@mtjrider is this something you can help with?

[mtjrider]

Yup. It's in my backlog for today.

I'll comment again later today.

[mtjrider]

Yup. It's in my backlog for today.

I'll comment again later today.

Checking in.
I'm wrapping up a few other actions today and can get this knocked out in the afternoon.

[jakirkham]

@mtjrider did you put something together? Do you need a review?