(cherry picked from commit d23ae49)

(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)

…#15258) [backport]

(cherry picked from commit 2447601)

* update c_malloc's to csize_t

(cherry picked from commit 57f98da)

)"

This reverts commit f713c54.

* 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)

(cherry picked from commit fe18771)

(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)

- Previously, `winrelease` called `bundleNimbleExe`, which tries to clone
  nimble to `dist/nimble` unconditionally.
- Since nightlies source tarball bundles nimble, git couldn't clone
  because `dist/nimble` was already there.
  This leads to 1.0.x couldn't be built with nimble bundled.
- The fix backports the logic from Nim >= 1.2.8 which can check if
  `dist/nimble` was bundled by the source archive.
  With this fix we can re-enable bundling of nimble to the source
  archive for 1.0.x.

(cherry picked from commit d4c2e2c)