Utilize babel-preset-latest instead of babel-preset-2015

What does this MR do?

Replaces babel-preset-2015 with babel-preset-latest which includes presets for es2015, es2016, and es2017. This is the recommended base preset by the maintainers of babel.

Are there points in the code the reviewer needs to double check?

Nope.

Why was this MR needed?

Prevents us from needing to update our config whenever new ECMAScript specs are adopted, we can simply yarn upgrade babel-preset-latest instead.

Screenshots (if relevant)

n/a

Does this MR meet the acceptance criteria?

• [ ] Changelog entry added
• [ ] Documentation created/updated
• [ ] API support added
• Tests
  • [ ] Added for this feature/bug
  • All builds are passing
• Conform by the merge request performance guides
• Conform by the style guides
• Branch has no merge conflicts with master (if it does - rebase it please)
• Squashed related commits together

What are the relevant issue numbers?

related to #27486 (moved)