Enabling alias parsing in pnpm_workspace_yaml

[thavaahariharangit]

What are you trying to accomplish?

Fixing the Bug related to this workflow

Error:

updater | 2025/01/20 14:45:53 ERROR <job_950629041> Error during file fetching; aborting: Alias parsing was not enabled. To enable it, pass `aliases: true` to `Psych::load` or `Psych::safe_load`.
updater | 2025/01/20 14:45:53 ERROR <job_950629041> Alias parsing was not enabled. To enable it, pass `aliases: true` to `Psych::load` or `Psych::safe_load`.
updater | 2025/01/20 14:45:53 ERROR <job_950629041> /home/dependabot/dependabot-updater/vendor/ruby/3.3.0/gems/psych-5.1.2/lib/psych/visitors/to_ruby.rb:432:in `visit_Psych_Nodes_Alias'

Anything you want to highlight for special attention from reviewers?

Wrote new rspec to test pnpm-workspace-yaml
rspec ./spec/dependabot/npm_and_yarn/file_fetcher_spec.rb:2024

nil scenario rspec ./spec/dependabot/npm_and_yarn/file_fetcher_spec.rb:2039
valid scenario rspec ./spec/dependabot/npm_and_yarn/file_fetcher_spec.rb:2047
Recreated this error scenario rspec ./spec/dependabot/npm_and_yarn/file_fetcher_spec.rb:2057

And provided the fix

How will you know you've accomplished your goal?

Recreated the same error with RSpec and provided fixes for that

rspec ./spec/dependabot/npm_and_yarn/file_fetcher_spec.rb:2061

Ran CLI , Wrote 3 Rspec tests, and ensured specs are passing

Checklist

• I have run the complete test suite to ensure all tests and linters pass.
• I have thoroughly tested my code changes to ensure they work as expected, including adding additional tests for new functionality.
• I have written clear and descriptive commit messages.
• I have provided a detailed description of the changes in the pull request, including the problem it addresses, how it fixes the problem, and any relevant details about the implementation.
• I have ensured that the code is well-documented and easy to understand.

[robaiken]

While this change will resolve the issue in the example workflow, it's worth noting that the provided example project doesn't reflect a typical pnpm workspace that uses the catalog feature. Although this pr fixes the yaml parsing for the example repo, in a repo where catalog dependencies are used, the user will most likely encounter issues as it won't be able to properly resolve the cataloged dependencies after the yaml is parsed.

I don't believe that this will be a blocker to this change, but it's something worth thinking about.