[BUG] Properties in configuration override should be case-insensitive

[Buffelstoot]

Release version

v6.0.1

Describe the bug

In the configuration yaml files, you now need to camelCase the resourceId of the backends.

Expected behavior

Configuration file used to look like this:

backends:

• name: helloworldfromfuncapp
  properties:
  url: "https://helloworldfromprodfuncapp.azurewebsites.net/api"
  resourceid: "https://management.azure.com/subscriptions/[subscription Guid goes here]/resourceGroups/rg-apim-lab-prod/providers/Microsoft.Web/sites/helloworldfromprodfuncapp"

Actual behavior

Configuration file now needs to look like this:

backends:

• name: helloworldfromfuncapp
  properties:
  url: "https://helloworldfromprodfuncapp.azurewebsites.net/api"
  resourceId: "https://management.azure.com/subscriptions/[subscription Guid goes here]/resourceGroups/rg-apim-lab-prod/providers/Microsoft.Web/sites/helloworldfromprodfuncapp"

Reproduction Steps

1. run extractor
2. run publisher with configuration yaml including backends with lowercase resourceid

[github-actions]

  Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
  Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.

[guythetechie]

@Buffelstoot - thanks for raising this. The overrides in the configuration JSON should be case-insensitive. We'll address this issue.