feat: add yarnpkg/nm/hoist export

[ChALkeR]

What's the problem this PR addresses?

Bundling @yarnpkg/nm (due to subdeps) is large and not needed when one needs only a few exports from ./hoist file:

berry/packages/yarnpkg-nm/sources/buildNodeModulesTree.ts

Lines 1 to 4 in b3dfa91

	import {structUtils, Project, MessageName, Locator} from '@yarnpkg/core';
	import {npath, ppath} from '@yarnpkg/fslib';
	import {NativePath, PortablePath, Filename} from '@yarnpkg/fslib';
	import {PnpApi, PhysicalPackageLocator, PackageInformation, DependencyTarget} from '@yarnpkg/pnp';

But hoist.ts is a zero-dep lib:

berry/packages/yarnpkg-nm/sources/hoist.ts

Lines 1 to 3 in b3dfa91

	/**
	* High-level node_modules hoisting algorithm recipe
	*

It's already built/distrubuted separately (see https://www.npmjs.com/package/@yarnpkg/nm?activeTab=code), just an entry in package.json was missing

Both its exports (and types) are already re-exported:

berry/packages/yarnpkg-nm/sources/index.ts

Lines 23 to 24 in b3dfa91

	export type {HoisterTree, HoisterResult} from './hoist';
	export {hoist, HoisterDependencyKind} from './hoist';

So this is not increasing public API surface, just adds a more convenient way to import it without pulling in the whole of @yarnpkg/core and @yarnpkg/pnp

How did you fix it?

Added ./hoist to exports to point to ./lib/hoist.js

Checklist

• I have read the Contributing Guide.

• I have set the packages that need to be released for my changes to be effective.

• I will check that all automated PR checks pass before the PR gets reviewed.

[larixer]

Makes sense. Please execute yarn version check -i and mark @yarnpkg/nm for patch release