Add a utility to identify Roarr location

I start pretty much every file with a variation of:

```js
import Logger from '../Logger';

const log = Logger.child({
namespace: 'createUpstreamHttpClientConfiguration',
});

```

`namespace` is most of the time the name of the file.

I am wondering if we could provide a utility to automate this, e.g.

```js
import log from 'roarr.macro';

```

that would transpile to a version above.

`Logger` file is usually simply used to add the package name to the context. That could be pulled from `package.json` or we could resolve location of the `Logger.js` file to always use as a base.

Start by inspecting the Logger file and the package.json context mentioned in the issue, then examine how Logger.js is resolved and how the proposed roarr.macro import could be transpiled. Done means a documented utility can derive the package context and file-based namespace for the shown logger pattern.

Written by the indexing model from the issue text.