Split client & serverside imports

Currently imports work with a single simple import statement, e.g.

import googleAnalytics from '@analytics/google-analytics'

This is great for dev ergonomics but causes issues with typescript because the serverside code can have different types than the client code 😅. Bummer! Reference issue in TS repo

So it appears we need a different approach to this.

It will most likely look something like this with client and server import paths

// import client side code for browser
import googleAnalytics from '@analytics/google-analytics/client'

// import server side code for node enviroment
import googleAnalytics from '@analytics/google-analytics/server'

Not as pretty but this should solve typescripts inability to resolve the correct type files.

Open to suggestions if anyone has ideas on this 😃

Start by reviewing how the @analytics/google-analytics package currently exposes its single import and its TypeScript declarations. Compare the client and server type requirements described in the issue, then determine how separate /client and /server imports should resolve. Done means both environment-specific imports resolve with the correct types.