BUG: Action fails when using non-standard config file

[dtrexler]

Describe the bug
The pagerduty:service:create action fails when overriding backstage configuration via command line arguments.

For example, the backstage helm chart overrides the default app-config.yaml file with a different one (example) so when using the helm chart, this action fails. However this applies to any non-standard configuration file.

To Reproduce
Steps to reproduce the behavior:

1. Rename the app-config.yaml file to anything else, ex. app-config.bug.yaml
2. When starting the backend, use the --config app-config.bug.yaml flag
3. Start a template using the pagerduty:service:create action
4. The action should fail due to not being able to load the config

Expected behavior
The action should inherit the configuration from the backend, rather than trying to reload it.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10
• Version Node 18.19.0

Additional context
Looking into the code, the problem seems to stem from the loadBackendConfig call, as far as I am aware, this function was only meant to be called once when initializing the backend and any plugin should inherit from it, so I am not sure how to fix it without breaking compatibility with legacy systems relying on this.