[No QA] Clean out unused routes

[roryabraham]

Details

Removes a number of unused screens and routes.

Fixed Issues

$ none, just general cleanup.

Tests

Just general regression testing. Run the app and make sure various routes work.

QA Steps

None – just regression testing.

Tested On

• Web
• Mobile Web
• Desktop
• iOS
• Android

[roryabraham]

cc @iwiznia 99% sure none of these routes are used anymore since we moved to the LoginWithShortLivedToken

[iwiznia]

Yep, I think these are all unsued now

[Julesssss]

Looks like a thorough clean up 👍

[Julesssss]

Not merging due to N6 hold, just to be safe.

[Julesssss]

N6 hold is over, merging.

[OSBotify]

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

[OSBotify]

🚀 Deployed to staging by @Julesssss in version: 1.1.8-10 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

[OSBotify]

🚀 Deployed to production by @roryabraham in version: 1.1.10-2 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

[marcaaron]

I think the ValidateLogin page should not have been removed in this PR. See this issue.

Maybe we assumed that because other routes with a /v were changing that all could be changed, but this behavior is now missing from the app.

App/src/pages/ValidateLoginPage.js

Lines 18 to 30 in 79eafd4

	class ValidateLoginPage extends Component {
	componentDidMount() {
	const accountID = lodashGet(this.props.route.params, 'accountID', '');
	const validateCode = lodashGet(this.props.route.params, 'validateCode', '');
	validateLogin(accountID, validateCode);
	}
	render() {
	// Don't render anything here since we will redirect the user once we've attempted to validate their login
	return null;
	}
	}