feat: UTRP v2 migration

[doprz]

TODO

• activeSchedule is not updated after switching to the new schedule
• If a schedule with the name UTRP v1 Migration already exists for some reason, it might cause bugs
• After redirecting to UT login (if not logged in), retry course migration (TODO)
• Add migration to onUpdate
• Calling UTRP v2 migration from onUpdate didn't seem to work properly with pnpm run build:watch but manually pressing the Migrate UTRP v1 courses button worked. pnpm run dev works too.

Issues that need to be resolved

Quoted from @Samathingamajig

• Doesn't work when not logged into ut
• Chrome warns in the console that in the future, cookies will not work when we do a network request like how we are doing it now, so might need to open a new tab (ideally a hidden/background tab, if those exist) instead
• Doesn't yet try to read from chrome.storage.sync for the existing classes

It does work enough such that a url to the class info page can get all the course info needed

_{Huly®: UTRP-289}

---

This change is 

[IsaDavRod]

Modify text to remove migration language and match the language on the Figma

Change button color to ut-green to make the button stand out more

Move the announcement section above the Useful Links section

[doprz]

Modify text to remove migration language and match the language on the Figma

Change button color to ut-green to make the button stand out more

Move the announcement section above the Useful Links section

Some thoughts:

• I'm ok with using ut-burntorange or ut-green but I do like ut-burntorange more.
• Since the migration is a one time thing it shouldn't be above the Useful Links section because of UI/UX principles unless we add a toggle to only show it once.

[IsaDavRod]

Modify text to remove migration language and match the language on the Figma
Change button color to ut-green to make the button stand out more
Move the announcement section above the Useful Links section

Some thoughts:

• I'm ok with using ut-burntorange or ut-green but I do like ut-burntorange more.
• Since the migration is a one time thing it shouldn't be above the Useful Links section because of UI/UX principles unless we add a toggle to only show it once.

Thank you for your thoughts. Let’s use ut-green to make it stand out. Since we’re adding courses, we can add a green button in the branding for that purpose.

For now, the migration announcement is only displayed above the Useful Links section. Most users will open the calendar for the first time and experience immediate stress when they see that their saved schedule and hard work is gone. If the migration is automatic and the button serves as a “backup” in case of failure, then we can move the Migration Announcement section below the Useful Links section.

If we want to stick to UI/UX principles, the Migration section should only appear once and be hidden if the schedule is successfully migrated. In that case, we can implement a toggle “migrationComplete” that stores and sets to true after the user completes their migration.

Style changes:

[DereC4]

Derek Chen will return

[doprz]

LGTM

[Samathingamajig]

note: we're going to (attempt to) do a large-scale test at the meeting tonight

[IsaDavRod]

Tested it, it works. LGTM