Use multi package build

[matteolimberto-da]

This PR introduces a multi-package.yaml file. This means you can call daml build on a single package and it will take care of building all dependencies for you.

I'll merge it after you've upgraded to the latest 3.4.7 SDK.

Still a bit of work to do to fix CI, as a bunch of scripts will need to be modified, but overall the setup will be way simpler.

[brianweir-da]

Thanks @matteolimberto-da for looking at this. I'll provide a review when the CI/scripts/etc are updated.

[matteolimberto-da]

Thanks @matteolimberto-da for looking at this. I'll provide a review when the CI/scripts/etc are updated.

Thanks! I'll merge this commit as-is into Karen's branch in order to make her life easier when it comes to building packages. Will then modify CI / scripts on a separate branch.

Basically my idea is

• get rid of the scripts to put dependencies into the right place
• just use packell to validate a package hasn't been released / perform dependencies upgrades

Easier said then done :)

[karenstaner-bit]

Removed symlinks and adopted multi-package build across daml-finance.
Key changes:

• Removed all .daml symlink-based package-databases
• Standardized every daml.yaml to use explicit data-dependencies
• Cleaned and rebuilt the entire dependency DAG
• Verified the structure with daml clean --all, daml build --all, and daml test --all
• Added Splice DARs to lib/ and updated paths to avoid local symlink references
• Removed obsolete symlink references across all packages
• Ensured no remaining symlink paths through full repo grep

Next steps (separate PR):

• Update Packell to work with the new multi-package dependency model
• Align Packell with DPM-compatible workflows

[dasormeter]

Please remove daml.yaml in the root of the project if you are making use of multi-package.yaml

The presence of both in the same scope leads to confusion / unexpected behaviour