[feat]: [PL-24913]: Add the support for create and update file in bitbucket server

[DeepakPatankar]

No description provided.

[allofthesepeople]

mostly comments and suggestions.

[allofthesepeople]

please handle these errors. Aware they're repetitive but could be more palatable with something like:

type multipartWriter struct {
    w mime. Writer
    err error
}

func (multipartWriter *mw) Write(f, v string) {
    if mw.err == nil {
        return
    }
    if v == "" {
        return
    }
    _, err = mw.WriteField(f, v)    
}

case *contentCreateUpdate:
    var b bytes.Buffer
    mw := multipartWriter{w: multipart.NewWriter(&b)}
    mw.write("content", string(content.Content))
    mw.write("message", content.Message)
    mw.write("branch", content.Branch)
    mw.write("sha", content.Sha)
    if mw.err != nil {
        return nil, fmt.Errorf("error writing multipart-content. err: %s", mw.err)
    }

see https://go.dev/blog/errors-are-values for background

[DeepakPatankar]

Did this change in another PR

[allofthesepeople]

is there a reason to check for empty value? Or in the name of readability might it be easier to pass on the empty fields? (there might be, I'm unfamiliar with the API)

[DeepakPatankar]

For some of the cases this values are not event required for the bitbucket API, hence I added this check that if the value is not null then don't add this value to multipart data

[allofthesepeople]

would a name like "multipartContent" or "multipartUploadContent" be better here?

Also suggest removing the json tags as it's a little confusing to the reader; the purpose of this struct appears to be in the case where json is not used.

[DeepakPatankar]

the current design in scm service is that whenever we are calling the client.do method, we pass it the json value and the client.do method converts it into the multipart data.
Because of which we cannot name it to multipartContent