[BUG] translateRequiredQueryParameters: "query" not honored by publisher

[martin2176]

Release version

v7.0.3

Describe the bug

Here is the scenario:
I have an API Spec with Query parameter required: true.
When I import it in APIM, I uncheck the box "Include required query parameters in operation templates"
This will cause the Query parameters not to be covered to template parameters. So far good.
I extract using API Ops and republish . In publisher override, I have
translateRequiredQueryParameters: query
However publisher publishes with query parameters as url template.
When I run publisher in trace mode, I can see it is making 2 PUT calls.
1st PUT call have "translateRequiredQueryParameters : query"
2nd PUT call have no attribute translateRequiredQueryParameters . So default would be template
(This may be the reason )

Expected behavior

publisher override translateRequiredQueryParameters: query
publisher should honor this override and should not convert "required" query parameters to url template parameters

Actual behavior

publisher always convert "required" query parameters to url template regardless of the setting in publisher override configuration file

Reproduction Steps

import a spec which have a query param as required
verify the api spec is imported with required query parameter as query parameter (not as template parameter)
extract with apiops
create a publisher api override configuration

apis:
  - name: <api name>
    properties:
      translateRequiredQueryParameters: query

run publisher
validate the API that is published. Will find that the "required" query parameters are converted to template parameter

//I tried with and without double quotes around query. same result

[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.