11 implement component mission protection system

[peterohanley]

Describe your changes

What changes have you implemented?

I have extracted the src folder of the HARDENS repo and other required folders (firmware) and replaced the submodule with it so we can make changes. I have started converting the frama-c specs to cn specs.

Issue ticket number and link

It is a partial fix for #11

Checklist before requesting a review

• I have performed a self-review of my code
• My code matches the coding standards and I have ran the appropriate linters
• I included documentation updates for my code
• I extended the test suite and the tests run by the CI to cover my code
• I assigned a Milestone to this PR
• I assigned this PR to a Project
• I assigned this PR appropriate Labels

[peterohanley]

If you limit the diff to only one commit at a time it is much easier to parse the changes.

[peterohanley]

This was mentioned as the idiomatic way to do this here but in a header file this way produces multiple copies the linker will choke on and in a source file the value won't be available to cn in other source files.

[podhrmic]

Pre-review:

• HARDENS submodule can be removed
• files currently in HARDENS folder should be pumped up by 1 level - so HARDENS/src will become src (I cannot even checkout the branch now)
• hardware folder can be removed - AFAIK there are no specs there?

[podhrmic]

• Coding standards: we don't have linters yet, so I am happy skipping that point for now
• Docs: can be updated in a separate MR

[peterohanley]

• HARDENS submodule can be removed

I have removed it in the first commit dcf8423

• files currently in HARDENS folder should be pumped up by 1 level - so HARDENS/src will become src (I cannot even checkout the branch now)

Apparently not in the right way.

• hardware folder can be removed - AFAIK there are no specs there?

It's in the include path, but it can be stripped down further.

[podhrmic]