Remove LGTM badges from README.md

[ThibFrgsGmz]

Originating Project/Creator
Affected Component	README.md
Affected Architectures(s)	N/A
Related Issue(s)	N/A
Has Unit Tests (y/n)	N/A
Builds Without Errors (y/n)	N/A
Unit Tests Pass (y/n)	N/A
Documentation Included (y/n)	N/A

---

Change Description

Removes LGTM badges from the project homepage. Currently the badget shows "lgtm invalid".

Rationale

See:

• Switch to Github Actions Code Scanner #1739
• Delete .lgtm.yml #1744
• Delete .lgtm.js #1745

Testing/Review Recommendations

I spotted some instructions for LGTM in the code base like :

fprime/Fw/Types/Serializable.cpp

Line 60 in 91c578e

SerializeBufferBase& SerializeBufferBase::operator=(const SerializeBufferBase &src) { // lgtm[cpp/rule-of-two]

fprime/Fw/Types/StringType.cpp

Line 105 in 91c578e

StringBase& StringBase::operator=(const CHAR* other) { // lgtm[cpp/rule-of-two]

fprime/Svc/FileDownlink/FileDownlink.cpp

Line 152 in 91c578e

const sourceFileNameString& sourceFilename, // lgtm[cpp/large-parameter] dictated by command architecture

fprime/Svc/FileDownlink/FileDownlink.cpp

Line 153 in 91c578e

const destFileNameString& destFilename, // lgtm[cpp/large-parameter] dictated by command architecture

I don't know if we should delete them because they would be deprecated, i.e. I don't know if CodeQL takes them.

Future Work

None

[thomas-bc]

Inline alert suppression using //lgtm or similar is not currently supported by GitHub Code Scanning. However the comment will show when the alert displays the code -- so it's still meaningful to the reviewer. Also it may become a feature in future versions of GitHub Code Scanning, or any other tool we might adopt in the future. So I would argue that keeping the comments in is a good choice.