chore: drop node version 12

[rishabh3112]

What kind of change does this PR introduce?
chore.
Drop node v12 as suggested by @alexander-akait

Did you add tests for your changes?
Nope

If relevant, did you update the documentation?
Nope

Summary

Does this PR introduce a breaking change?

Other information

#3243 (comment)

[codecov]

Codecov Report

Merging #3251 (03ee3ab) into next (e6f6e25) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             next    #3251   +/-   ##
=======================================
  Coverage   92.08%   92.08%           
=======================================
  Files          23       23           
  Lines        1731     1731           
  Branches      519      519           
=======================================
  Hits         1594     1594           
  Misses        137      137           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e6f6e25...03ee3ab. Read the comment docs.

[snitin315]

I suppose we should point it to the next branch.

[rishabh3112]

I suppose we should point it to the next branch.

I don't think so as next branch is pretty outdated to qualify for a major release (290+ commits behind).
Also, as per @alexander-akait 's comment above, we need a major release now asap. So, master should be the location.

[snitin315]

That branch is indeed far behind. Then, should we do a release before merging this PR to master? WDYT @alexander-akait

[alexander-akait]

I think next is outdated, but there is simple list of improvements #2879, so I think we can start new branch next (rename old next to next-old), move already done work to new next + solve TODOs from list, here little bit more work for us

[alexander-akait]

PR was closed because I rename next to next-old, I will not remove branch because we need to move code here.

So let's start the new next and merge it in next

[rishabh3112]

I think next is outdated, but there is simple list of improvements #2879, so I think we can start new branch next (rename old next to next-old), move already done work to new next + solve TODOs from list, here little bit more work for us

On it 👍🏽

[snitin315]

Let's also not merge any more PRs to master, to avoid rebasing.

[alexander-akait]

@snitin315 I think merging deps will not be a problem, rebasing it not hard here, but other PRs - yes