[Spritelab] Continue migrating away from v3 animations

[ajpal]

Follow up to #35939

1. un-deletes the levels deleted in that PR (I didn't realize deleting levels wasn't supported)

2. Removes the start_animations from those levels (instead of deleting the whole level, just sets start_animations to nil.

3. Replaces the following v3 animations with v1 animations using the new custom_animations api endpoint
   
   code snippet to find/replace:

import os
import csv

csv_file = '/Users/anjali/Downloads/animations.csv'
animations = []
with open(csv_file, 'r') as f:
    reader = csv.reader(f)
    for row in reader:
        animations.append({'name': row[0], 'old': row[1], 'new': row[3]})

levels = os.listdir('/Users/anjali/code-dot-org/dashboard/config/scripts/levels')
for level in levels:
    with open(level, 'r') as file:
        filedata = file.read()
    
    for animation in animations:
        filedata = filedata.replace(animation['old'], animation['new'])
    
    with open(level, 'w') as file:
        file.write(filedata)

Next step: Continue building out the custom_animations bucket on S3 and replacing v3 animations with those.

Links

• spec
• jira

Testing story

Reviewer Checklist:

• Tests provide adequate coverage
• 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

[ajpal]

Second find and replace commit:

https://docs.google.com/spreadsheets/d/1nP9NP8mYqWkAuy7xleWWooqTqC5wjU3L_jWuefQ2sQo/edit#gid=458531085
(Same python snippet)

[maddiedierker]

i can't comment on the file itself, but i think the change to schema_cache.dump should be reverted here

[maddiedierker]

once the change to schema_cache.dump is reverted, this looks good to go!