Implement first green query for Arduino C++ developers

[olegoaer]

This pull request introduces a new CodeQL query to help prevent accidental hardware damage on Arduino devices by detecting unsafe usage of the EEPROM.write method inside the main loop() function. It also adds an example C++ file that illustrates the problematic pattern.

However, the .expected file is missing for now.

[TitouanCharrier]

La Guard est imparfaite,
Elle suppose que le if soit suffisemment discriminant pour protéger le matériel ce dont nous n'avons pas de preuve

[TitouanCharrier]

Cette détéction de write n'est pas transitive, si une fonction externe appel un write et que cette fonction est présente dans la loop, la requête ne descend pas dans le call graph https://codeql.github.com/docs/codeql-language-guides/refining-a-query-to-account-for-edge-cases/

from Constructor c, Field f where f.getDeclaringType() = c.getDeclaringType() and f.isPrivate() // check for constructor initialization lists as well and not exists(ConstructorFieldInit i | i.getTarget() = f and i.getEnclosingFunction() = c) // check for initializations performed indirectly by methods called // as a result of the constructor being called and not exists(Function fun, Assignment a | c.calls*(fun) and a = f.getAnAssignment() and a.getEnclosingFunction() = fun) // ignore cases where the constructor source code is not available and exists(c.getBlock()) select c, "Constructor does not initialize fields $@.", f, f.getName()

On pourrait les remplacer par

exists(Function loopFn | loopFn.getName() = "loop" and loopFn.calls*(call.getEnclosingFunction()) )

Pour ajouter la transitivité