feat-notification: Notification conversion step for harness

[vanisrikanithi]

Notification go-conversion:
Added "Notification" support to go-convert specific to jenkins migration.

Norification Jenkins Trace:

vani_notification__18.json

go run main.go jenkinsjson --downgrade ~/go/vani_notification__18.json

Harness Notification Pipeline is here.

Notification harness pipeline step:

- step:
    identifier: notifyendpointsca9fc8
    name: Notification
    spec:
      image: plugins/webhook
      settings:
        content_type: application/json
        debug: "true"
        method: <+input>
        password: <+input>
        template: '{"status": "Build Successful", "job": "${env.JOB_NAME}", "buildNumber": "${env.BUILD_NUMBER}"}'
        urls: <+input>
        username: <+input>
    timeout: ""
    type: Plugin

[vanisrikanithi]

Hello @Ompragash ,

Could you please review the Notification conversion PR and provide your comments if there are any?

Thank you.

[Ompragash]

looks like the template value is being formatted with a newline, which will throw an error in Harness. To fix this, ensure the template value is on a single line in the generated YAML. Once fixed, the changes can be merged

              identifier: Stage_null87edb4
              name: Notify
              steps:
              - step:
                  identifier: notifyendpointsca9fc8
                  name: Notification
                  spec:
                    image: plugins/webhook
                    settings:
                      content_type: application/json
                      debug: "true"
                      method: <+input>
                      password: <+input>
                      template: '{"status": "Build Successful", "job": "${env.JOB_NAME}",
                        "buildNumber": "${env.BUILD_NUMBER}"}'
                      urls: <+input>
                      username: <+input>
                  timeout: ""
                  type: Plugin

[vanisrikanithi]

@Ompragash, YAML serializers typically have a default line length limit. If the string exceeds this limit, the serializer splits it into multiple lines.

Happy Path: I have copied the conversion step and pasted it in harness yaml, once I save the yaml it is automatically formatting the template.
Harness Test Pipeline

Could you please check it and confirm the changes?