Remove absolute paths used in pdm.lock file

[hari-kuriakose]

What

• Fix absolute path for local dependency being used in pdm.lock file for backend
• Add updated pdm.lock file for backend
• Remove unnecessary pdm.lock file for tool registry as it will always be a local dependency

Why

Indirect local dependencies usually need to be added in their own projects as: https://pdm-project.org/latest/usage/dependency/#local-dependencies.

However, such indirect local dependencies which are not direct dependency of main project appear as absolute paths in pdm.lock of main project, making it impossible to check in the lock file.

How

1. Add all indirect local dependencies too in the main project (main project here is backend).
2. Add any local dependencies without version constraints in the sub-project, where the assumption is they are added as direct dependencies in main project itself (sub-project here is tool-registry).
3. This will cause PDM to add the dependencies correctly in the pdm.lock file in the main project without using any absolute paths.

Notes on Testing

New generated pdm.lock file for backend does not contain any absolute paths.

Checklist

I have read and understood the Contribution Guidelines.