Use base 10 when calculating memory

[fatadel]

Closes #5485.

I hope I correctly understood the issue and the following intentions. Also, there were 2 different opinions when we were discussing the issue:

1. Use base 10 numbers everywhere;
2. Selectively use base 10 vs base 2 numbers;

I agree with opinion 1, as it makes things easier and consistent imo. But feel to propose other solutions.

Example profile: before / after.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.57%. Comparing base (0693702) to head (dd02b5e).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5810   +/-   ##
=======================================
  Coverage   85.57%   85.57%           
=======================================
  Files         320      320           
  Lines       31448    31448           
  Branches     8570     8656   +86     
=======================================
  Hits        26911    26911           
  Misses       4106     4106           
  Partials      431      431           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[canova]

Hey @fatadel, thanks for the PR! The example profile you shared is a regular sampling profile. Could you capture and share a memory profile using for example the "Native Allocation" feature in the about:profiling?

[fatadel]

Thanks for the hint, @canova! Updated the links.

[canova]

Looks good to me, thanks!

Btw, I updated the title to fix the typo and also changed the capitalization.

[canova]

Suggested change

	expect(formatGigaBytes(1234567890, 3, 2, 1024)).toBe('1GB 234MB 568KB');
	expect(formatGigaBytes(1234567890, 3, 2, 1000)).toBe('1GB 234MB 568KB');

nit: it would be good to change these precision values to 10 based too. (here and below)

[fatadel]

Thanks for your review and for the nit, @canova! I've incorporated it, will merge now.