Add evergreen raspi build config

[niranjanyardi]

Issue: 412446243

Add CI actions for raspi evergreen build.
Remove CI actions for raspi build.

[niranjanyardi]

/gemini review

[gemini-code-assist]

Code Review

This pull request updates the Raspberry Pi build configuration to a new 'evergreen' version. This involves renaming the configuration file from .github/config/raspi.json to .github/config/evergreen-raspi-arm-hardfp.json and updating platform identifiers within it. These changes seem to align well with the stated goal of adding CI actions for an evergreen raspi build and removing the old ones.

One general question regarding the overall change: The docker_service field (line 2 of the new file) remains "raspi". With the transition to an 'evergreen' setup, was there any consideration to update this field? Is "raspi" still the correct and intended service identifier for this new configuration, or should it perhaps also reflect the 'evergreen' aspect or a more specific version if the underlying Docker service context has changed? (Note: As this line isn't directly modified in the diff, this is a broader query about the configuration's completeness.)

Please see the specific review comment below regarding a naming detail within the includes section.

Summary of Findings

• Potential Naming Inconsistency in Configuration: The name field within the includes section of the evergreen-raspi-arm-hardfp.json configuration file is "raspi-arm-hardfp", while other related identifiers use the "evergreen-raspi-arm-hardfp" naming. Clarification is requested to ensure this distinction is intentional and correct, as an oversight could lead to misconfiguration.

Merge Readiness

The PR makes a clear and targeted change to update the Raspberry Pi build configuration for an 'evergreen' system. However, there's one point regarding a naming convention within the JSON configuration (detailed in the review comment) that would benefit from clarification to ensure its accuracy. Addressing this point will help confirm the configuration's correctness before merging.

Therefore, I recommend clarifying the noted point. As a reviewer, I am not authorized to approve pull requests; please ensure this PR undergoes any further necessary reviews and approvals according to your team's policies before merging.

All comments addressed