Action: Patch needs to support yaml containing string values.

[etsauer]

What does this PR do?

I ran into a scneario this week where our patch support fails to handle patch file that contain quotes strings, e.g.:

spec:
  tags:
    - name: "2.7"
      importPolicy:
        scheduled: true

This PR adds a test of this scenario, as well as a fix to the role to handle it better.

How should this be tested?

molecule test

Is there a relevant Issue open for this?

n/a

Who would you like to review this?

cc: @redhat-cop/openshift-applier

[oybed]

The more I think about this, I don't think I agree with the solution. i.e.: we're now processing it as yaml (and require the file to be written in yaml). This should just be a string of the content of the file. In other words, we are now making the openshift-applier be "smarter" about this content and it shouldn't be

[etsauer]

@oybed I added a test showing that json still works as well. The only thing functionally that we are doing is a {yaml|json} to json conversion of the contents of the file, so that we don't have to deal with complex escaping of \n and \t characters in the string.

[etsauer]

I should also mention that the current implementation of patch ONLY works for YAML. if you run the tests I added aginst the role in master, you'll see that even the simple tests we had will fail if you use a json formatted patch file.

[oybed]

LGTM