Replace old script markdown with updated names

[hannahbergam]

Issue:
CSD resources were cloned when they were still in a broken state (i.e. csd3/2023 instead of csd/2023).

Approach:
A find and replace of all resources with the markdown 'csd1/2023', 'csd2/2023', etc. -> 'csd/2023'.

Future work:
These resources still might not be pointing to the correct unit. For example, we might want to make sure the resource in the focus-on-coding4a-2023 unit actually points to a resource from focus-on-coding4a/2023. However, because we're not sure those resources exist in those places (and are sure they exist in csd), we elected to point to the correct CSD location instead of doing the larger work of finding the perfect name and copying over the resources.

Example:
Here is one of the resources that was copied, before and after the fix.

Before:

After:

Links

• spec:
• jira ticket: https://codedotorg.atlassian.net/browse/TEACH-395

Testing story

Deployment strategy

Follow-up work

Privacy

Security

Caching

PR Checklist:

• Tests provide adequate coverage
• Privacy and Security impacts have been assessed
• Code is well-commented
• New features are translatable or updates will not break translations
• Relevant documentation has been added or updated
• User impact is well-understood and desirable
• Pull Request is labeled appropriately
• Follow-up work items (including potential tech debt) are tracked and linked

[bethanyaconnor]

Wooo! Can you make a ticket addressing the fact that these point to the wrong course version sometimes? I still don't know if that's worth fixing but I still want to think about it :)

[tess323]

😍

[hannahbergam]

Wooo! Can you make a ticket addressing the fact that these point to the wrong course version sometimes? I still don't know if that's worth fixing but I still want to think about it :)

Added this to 'Candidates for Up Next'! https://codedotorg.atlassian.net/browse/TEACH-508