This PR adds the route and page for Sage inside Spire.
The page itself is a wrapper around an iframe that points to the latest eqsage--It will take whatever is latest in the production site. This is achieved locally optionally by pointing to a locally running dev server from the webpack config or by reverse proxying from the go backend to the eqsage production site, https://eqsage.vercel.app . I figure with the rapid development of eqsage it would be better to not lock in per version and build the SPA since this isn't entirely functional yet.
This PR adds the route and page for Sage inside Spire. The page itself is a wrapper around an iframe that points to the latest eqsage--It will take whatever is latest in the production site. This is achieved locally optionally by pointing to a locally running dev server from the webpack config or by reverse proxying from the go backend to the eqsage production site, https://eqsage.vercel.app . I figure with the rapid development of eqsage it would be better to not lock in per version and build the SPA since this isn't entirely functional yet.