text: Title: Allow dvc.yaml templating from non default params files
  Body: Hi! First of all, thanks for your amazing work, I love it and I'm trying to push our team to use it on daily basis.
  
  I'm trying to have multiple pipelines to handle different behaviors in a RAG library : a synthetic dataset generation and a RAG execution.
  
  I have divided a folder `pipelines` into  2 subfolders `rag` and `synth_dataset_generation`, which have their own `dvc.yaml` and `params.yaml`, but they have some parameters in common, in `global_params.yaml`, which I'm trying to use to template their respective `dvc.yaml`. However, no matter how I try to structure its reference, I always get a  `dvc.parsing.ResolveError: failed to parse 'stages.data_extraction.cmd' in 'pipelines/rag/dvc.yaml': Could not find 'input_data'`.
  
  I've tried to debug it with `dvc repro -vvvv` and it seems that the context stays empty from any key/value of `global_params.yaml` : 
  ```
  Context during resolution of stage data_extraction:
  {}
  ```
  
  I've stumbled upon this issue while dividing my main pipeline in 2 others, but I've explored this behaviour in a test repo and it seems impossible to template my `dvc.yaml` with values from a param file other than the default one. ([here is the link to it](https://github.com/Gwenn-LR/templating_dvc_with_parameters))
  
  So I was wondering if it was an expected behaviour or if you could add this feature  ?
  
  Thank you for your consideration. 