(cherry picked from commit d23ae49)

(cherry picked from commit d6161e7)

(cherry picked from commit 64aec6e)

(cherry picked from commit 2a8bf47)

The closed flag isn't a good design by any means, but let's have this
working first before I get rid of the flag and potentially create a
non-backportable commit.

(cherry picked from commit 957bf15)

(cherry picked from commit 15ff89c)

(cherry picked from commit 4096929)

* fixes #15210 [backport:1.2]

* use patched version of bigints library

(cherry picked from commit ff13f8c)

…#15258) [backport]

(cherry picked from commit 2447601)

(cherry picked from commit 4fb17bc)

* update c_malloc's to csize_t

(cherry picked from commit 57f98da)

(cherry picked from commit e08b802)

(cherry picked from commit a816102)

* fixes #15280 [backport:1.2]

* make tests green again

* adapt tests

(cherry picked from commit 3f00a73)

(cherry picked from commit b56432b)

* azure-pipelines: cache csources to speed up build

Building csources takes about 2-4 mins, and since it hasn't changed for
a long time, employ some caching to cut the time spent.

* azure-pipelines: remove ppa avoidance configs

Testing shows that there aren't any difference between having this and
not having it, so removing this to simplify the code.

(cherry picked from commit c292c57)

* nativesockets docs minor [backport: 1.2]

* remove annoying messages

(cherry picked from commit a41b243)

(cherry picked from commit 8b66412)

… [backport:1.2]

(cherry picked from commit cbdda63)

(cherry picked from commit c2434d9)

* nimStackTraceOverride: enable stack traces in exceptions

This is a two-step stack trace collection scheme, because re-raised
exceptions will collect multiple stack traces but use them rarely, when
printing info about an uncaught exception, so it makes sense to only do
the cheap stack unwinding all the time and the relatively expensive
debugging information collection on-demand.

`asyncfutures` implements its own `$` proc for printing
`seq[StackTraceEntry]`, so we have to add the debugging info there, just
like we do for the private `$` proc in `system/excpt`.

* cleaned up PR #15284

Co-authored-by: Ștefan Talpalaru <stefantalpalaru@yahoo.com>
(cherry picked from commit 1fae66e)

(cherry picked from commit e2d80b1)

(cherry picked from commit 22d0a39)

(cherry picked from commit eb2a496)

* fixes #15243 [backport:1.2]

(cherry picked from commit aa1d7fe)

(cherry picked from commit ff70ff5)

(cherry picked from commit 2288188)

This allows distributions to build Nim from the downloaded source
archive without an Internet connection.

(cherry picked from commit d4892e9)

On Windows, a successful call will have a trailing newline appended, so
strip that away before doing any checks.

(cherry picked from commit e3eae3f)

This commit gets rid of buildNimble in favor of the simpler
bundleNimbleExe, which does pretty much the same thing.

(cherry picked from commit 3919f0a)

(cherry picked from commit fe18771)

(cherry picked from commit 0ac74dd)

This test runtime tends to hover around the 5s mark depending on how
loaded the system currently is. This causes the test to fail a lot
during CI, per analytics:
https://dev.azure.com/nim-lang/Nim/_test/analytics?definitionId=1&contextType=build

Give the test an extra 2 seconds to account for unrelated overhead.

(cherry picked from commit 83435fe)

(cherry picked from commit c7ccbfa)

(cherry picked from commit f1d81dc)

Since #8296, fgSetColor is no longer a global. These commands were
probably left out from the change as an oversight, so some tests have
been added to make sure this won't happen again.

(cherry picked from commit d1af958)

(cherry picked from commit c664fb2)

(cherry picked from commit a4c2839)

Co-authored-by: Igor Ribeiro de Assis <igor.ribeiro_de_assis@zeiss.com>
(cherry picked from commit 42c180c)

(cherry picked from commit da4aa2e)

This reverts commit 3f00a73.

(cherry picked from commit d4022eb)

(cherry picked from commit d4c2e2c)