[docs] no more migrators from expo build

[quinlanj]

Why

Are people still migrating from classic builds? It's been so long since we've shut it off, it may be better off archived.

How

• move expo build migration to archive
• add redirects to archive

Test Plan

• manually inspected

Checklist

• Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md).
• Conforms with the Documentation Writing Style Guide
• This diff will work correctly for npx expo prebuild & EAS Build (eg: updated a module plugin).

[amandeepmittal]

Instead of migrating it to /classic-updates/, I'd suggest archiving this doc under Classic Builds.

I know this deprecated doc contains info about page but the main focus I think is expo build to EAS Build.

[quinlanj]

@amandeepmittal one weird thing i noticed is that all builds documents are under the classic-updates folder and there is no classic-builds folder (now that you mention it, that's probably not intended?)

expo/docs/constants/navigation.js

Lines 474 to 477 in b6ff87f

	const archive = [
	makeSection('Classic Builds', [
	makePage('archive/classic-updates/building-standalone-apps.mdx'),
	makePage('archive/classic-updates/turtle-cli.mdx'),

What do you think about this plan:

• In this PR, we can make the classic-builds folder and move the article there
• in a followup pr, we could move everything else that was incorrectly classified under classic-updates to classic-builds. Happy to do it, if you'd like :)

[quinlanj]

Also can someone confirm that we actually do want to deprecate this doc

[amandeepmittal]

@amandeepmittal one weird thing i noticed is that all builds documents are under the classic-updates folder and there is no classic-builds folder (now that you mention it, that's probably not intended?)

expo/docs/constants/navigation.js

Lines 474 to 477 in b6ff87f

	const archive = [
	makeSection('Classic Builds', [
	makePage('archive/classic-updates/building-standalone-apps.mdx'),
	makePage('archive/classic-updates/turtle-cli.mdx'),

What do you think about this plan:

• In this PR, we can make the classic-builds folder and move the article there
• in a followup pr, we could move everything else that was incorrectly classified under classic-updates to classic-builds. Happy to do it, if you'd like :)

This sounds perfect! Apologies, I didn't pay attention to the classic-builds folder not existing before, but that's a great catch! Let's not block this PR, and I can follow up with migration from classic-updates to classic-builds 😄

[amandeepmittal]

Also can someone confirm that we actually do want to deprecate this doc

cc: @brentvatne

[expo-bot]

📘 Your docs preview website is ready!

[szdziedzic]

thanks!