fix(services/configurations): use terser instead of uglify

[homer0]

What does this PR do?

This is something I already did for the webpack plugin on homer0/projext-plugin-webpack#63 and I didn't do it here because I was sure the uglify plugin was already using terser...well, it wasn't.

The problem is that uglifyjs can't handle ES6+ code, so if you want to uglify that kind of code, you need to use terser.

I replaced rollup-plugin-uglify with rollup-plugin-terser and, the change that makes this breaking, I updated all the events settings for the new plugin:

- rollup-uglify-plugin-settings-configuration-for-node
+ rollup-terser-plugin-settings-configuration-for-node

- rollup-uglify-plugin-settings-configuration-for-browser
+ rollup-terser-plugin-settings-configuration-for-browser

- rollup-uglify-plugin-settings-configuration
+ rollup-terser-plugin-settings-configuration

How should it be tested manually?

Try to build a project with ES6 code for production (to trigger the uglify process), and of course...

yarn test
# or
npm test

[coveralls]

Pull Request Test Coverage Report for Build 132

• 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 100.0%

---

Totals
Change from base Build 131:	0.0%
Covered Lines:	1479
Relevant Lines:	1479

---

💛 - Coveralls