Feature/migrate html minifier terser

[multivoltage]

Checklist

• [x] run npm run test and npm run benchmark
• [x] tests and/or benchmarks are included
• [x] documentation is changed or added
• [x] commit message and code follows the Developer's Certification of Origin and the Code of conduct

Goal

I saw an issue of an user that ask support for html-minifier-terser in place of html-minifier. Only thing that change is that minify method is a promise.

Behavior using old html-minifier

Since in js we can do

function syncMethod(){
   return "hello";
}
const output = await syncMethod()

Even point-of-view will add the terser version which is Promise based, configuring options like this:

const minifier = require('html-minifier')
// optionally defined the html-minifier options
const minifierOpts = {
  removeComments: true,
}
  options: {
    useHtmlMinifier: minifier,
    htmlMinifierOptions: minifierOpts
  }

can be done also using html-minifier instead html-minifier-terser

[multivoltage]

In my small experience I prefer only await and async instead callback. But there are some case where we cannot wait a "line" but only start a "parallel" method. I will do an analysis next day.

If we agree to replace all callback with await async, do you you think I can put changes in that pr ?

[mcollina]

It's better to do the two things separately

[multivoltage]

Ok. I will try to use callback for this or. Thanks

[multivoltage]

@mcollina when you say to migrate all codebase to async await you are considering also for example readFile() or only calls "then()" for promises?

[mcollina]

All of it, yes.

[multivoltage]

I resume this PR since async flow was introduced

[mcollina]

CLosing for no activity

[multivoltage]

OK. I updated PR (like I said in the previous comment). Did you expect other changes?