This adds span creation and route parameterization to the experimental getStaticProps and getServerSideProps wrappers. In order to do the parameterization, we store the parameterized route( which is the same as the filepath of the page file) as a global variable in the code we add using the dataFetchersLoader and then pass it to the wrappers, which then replace the name of the active transaction with the parameterized route we've stored. It also adds basic error-capturing to the wrappers.

Open issues/questions (not solved by this PR):

• Because of prefetching, revalidation of static pages, and the like, the data fetching functions can run in the background, during handling of a route different from their own. (For example, if page A has a nextjs Link component pointing to page B, next will prefetch the data for B (and therefore run its data fetching functions) while handling the request for A. We need to make sure that we don't accidentally overwrite the transaction name in that case to B.
• There's more we should do in terms of error handling. Specifically, we should port much of the logic in withSentry into these wrappers also.
• Porting the error-handling logic will mean we need to deal with the domain question - how to keep reactivating the correct domain as we go into and out of data fetching and rendering functions.

(There are other items listed in the meta issue linked below, but the above are the ones directly relevant to the work in this PR.)

Ref: #5505