Part of QA03-039

Change-Id: Idbbbb1907653e82a623e1a929c1ffc1982d73174

Part of QA19-079

Change-Id: I71343ab333c18cbb1162a1f41c6846d8ddd846f3

Just not considering them as actual statements, as we were already doing
for pragma Annotate.

This prevents the production of meanlingless diagnostics
such as "statement never executed" on e.g. pragma Pure, which helps
readbility and reduces potential confusion.

Part of QA23-039

Change-Id: I08de62ecbf3bef083eb5556b28c4575f4808900b
(cherry picked from commit 6a07b72)

Now ignored for coverage reporting purposes, per QA23-039

Change-Id: I157021e030576d1e5ddf40a8323866496527fd8d
(cherry picked from commit c14663b)

Follow-up adjustments on change just introduced for QA23-039

Change-Id: I5d46be3c8449b0b0f9f6f75b38918e2445676de8
(cherry picked from commit 6952c0a)

The Tools main menu morphed into Analyze. Adjust text and redo
screenshots.

Rephrase the paragraph referring to possible warnings in
GNATtest scenarii.

For Q927-033

Change-Id: I198a96f35879d79d85a165ff6978383a4ea5d4db
(cherry picked from commit e6aceba)

gnatcov run --target=prepare was meant to let users prepare
for an execution that will just append trace entries to a trace
file, typically by running qemu separately. The preparation
consists in creating the trace file and storing a trace header
there.

This was removed based on the belief that this facility wasn't
used any more. It actually still is relied upon by a few scripts
involved in runtime certification activities, some currently
ongoing.

In the course of QA16-036. Part of QA27-024 for 18.

Change-Id: I719372cf9268d6964ff91d7e6a427acaeede1e09
(cherry picked from commit 00bdac3)

extracted from tests/OA05-051-sharedobjs, so it can be reused
by other tests.

Part of work for adding a test for QA27-024

Change-Id: Ibbec782ca23b464a076c599fa4aabae9873b05f8
(cherry picked from commit 9b80d2c)

So we can inspect traces out of --target=prepare, part of test
for QA27-024.

Change-Id: Ib158c10970f0479cce58dc435b5525137be0efbd
(cherry picked from commit 284e279)

Change-Id: Ia424345da9cdd729cfdc73529af52e85b609090e
TN: QA27-024
(cherry picked from commit f616f5f)

Change-Id: Ieb27d1e0a56633ca740b721d1fc0490e92df080b
TN: QA27-024
(cherry picked from commit af5073f)

R305-053

Change-Id: I324b9abf09acc9047de3f5e05ba7fe5280df92db
TN: PC20-040
(cherry picked from commit c825ab1)

Change-Id: Id09c41ad21c093c26dbbc991e293aa14363baaff
TN: QB14-023
(cherry picked from commit f2a1840)

On 18-sustained, GNATCoverage was previously built with Visual Studio
12. With the Secure control plane transition we have only Visual
Studio 17, take the opportunity to use a newer version of
Visual Studio

Ref: it/org/software-supply-chain/production-pipeline/issues#129

Fix GNATCoverage build on Windows

See merge request eng/das/cov/gnatcoverage!878

On 18-sustained, GNATCoverage was previously built with Visual Studio
12. With the Secure control plane transition we have only Visual
Studio 17, take the opportunity to use a newer version of
Visual Studio

Ref: it/org/software-supply-chain/production-pipeline/issues#129