Make it clear which @wasp imports are importing user-defined stuff, and which @wasp core stuff

[Martinsos]

e.g. currently import MyQuery from "@wasp/queries/MyQuery" imports user defined query, while import createNewUser from "@wasp/core/auth.js" Wasp defined function, and import useAuth from '@wasp/auth/useAuth.js' imports Wasp defined React hook.

They all look similar and it is hard for user to figure out what is Wasp defined and what is user defined! We got this feedback from a user.

We could standardize import paths in some way, so that Wasp defined stuff always starts in same fashion.

This might also become more trivial to solve (or solved inherently) once we implement inline JS and modules.

[sodic]

The import sytnax changed, but this remains a problem.

Related: https://github.com/wasp-lang/wasp/issues/284