fix: Added support for npm link

[Aukevanoost]

Linked to #55

This pull request improves the handling of npm-linked shared packages in both the main and remote builders, ensuring that edits to linked shared libraries trigger proper federation-only rebuilds during development. It also updates several dependencies to their latest patch versions for improved compatibility and bug fixes.

Linked shared package handling:

• Added the linkedSharedDirs utility to both src/builders/build/builder.ts and src/builders/remote/builder.ts, allowing the federation file watcher to monitor real source directories of npm-linked shared packages. This ensures that changes in linked libraries trigger federation rebuilds, even when Angular does not emit new outputs. [1] [2] [3] [4] [5] [6] [7] [8] [9]
• Refactored the build/watch loop in runBuilder to handle two rebuild triggers: Angular output and linked shared-package edits. Federation rebuilds are now properly serialized and triggered as needed, without missing changes from linked packages. [1] [2]

Dependency updates:

• Updated @softarc/native-federation to ^4.3.2 and @softarc/native-federation-orchestrator to ^4.5.2 in package.json and pnpm-lock.yaml for latest fixes and improvements. [1] [2] [3] [4]
• Updated transitive dependencies in pnpm-lock.yaml, including @emnapi/core, @emnapi/runtime, picomatch, and balanced-match for better stability and bug fixes. [1] [2] [3]

Other lockfile maintenance:

• Removed unnecessary optional: true flags from some dependencies in pnpm-lock.yaml to keep the lockfile clean. [1] [2] [3]

These changes improve the developer experience when working with npm-linked shared packages and keep dependencies up to date.