refactor: removeObject

[trim21]

This PR refactors Client.removeObject to TypeScript.

What's maintainers' option on this, is this an acceptable change?

ideally, refactered method should use async function and we can wrapped them with callbackify to handle potential latest callback function argument.

this also make it easier to add arguments, no need to do this:

    // backward compatibility
    if (isFunction(removeOpts)) {
      cb = removeOpts
      removeOpts = {}
    }

But currently, arguments are checked synchronously.

for example: callback can't catch the error throwed by method.

client.removeObject(null, '...', (err,result)=>{})

they need to catch null bucket name error like this:

try{
  client.removeObject(null, '...', (err,result)=>{})
} catch(e) {
  ...
}

after this PR, client.removeObject(null, '...', (err,result)=>{}) will not throw, but always return error to callback or promise reject.

also, mark callback style API as @deprecated

[aldy505]

LGTM

[prakashsvmx]

I too have evaluated alternatives and the suggestion. yes. We can go ahead with this for the flexibility it offers. 👍 @trim21

[trim21]

I too have evaluated alternatives and the suggestion. yes. We can go ahead with this for the flexibility it offers. 👍 @trim21

This make thing much easier

[trim21]

@prakashsvmx i mark callback style api as deprecated, hope this is not a problem

[trim21]

@kaankabalak

[prakashsvmx]

Tested.

- forceDelete
- versionId
- governanceBypass  w/o versionId

Changes look good to me.

[kaankabalak]

LGTM