chore: remove unused PROJECT from Earthfiles

[janishorsts]

The PROJECT command was used for the Earthly Cloud. This PR removes the command from all Earthfiles.

[github-actions]

🎉 Are we earthbuild yet?

Great progress! You've reduced "earthly" occurrences by 18 (0.29%)

📈 Overall Progress

Branch	Total Count
main	6173
This PR	6155
Difference	-18 (0.29%)

📁 Changes by file type:

File Type	Change
Go files (.go)	❌ +1
Documentation (.md)	➖ No change
Earthfiles	✅ -11

---

Keep up the great work migrating from Earthly to Earthbuild! 🚀

💡 Tips for finding more occurrences

Run locally to see detailed breakdown:

./.github/scripts/count-earthly.sh

Note that the goal is not to reach 0.
There is anticipated to be at least some occurences of earthly in the source code due to backwards compatibility with config files and language constructs.

[gemini-code-assist]

Summary of Changes

Hello @janishorsts, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request performs a targeted cleanup operation across the repository by removing the PROJECT earthly-technologies/core declaration from multiple Earthfiles. This directive was identified as unused, and its removal streamlines the build configurations, enhancing clarity and reducing unnecessary boilerplate. The change is purely a maintenance task aimed at improving the overall health and simplicity of the project's build definitions.

Highlights

• Configuration Cleanup: The PROJECT earthly-technologies/core declaration has been removed from numerous Earthfiles, indicating it is no longer required or used.
• Scope of Change: This change affects a wide range of Earthfiles, including those in inputgraph, release, and various tests directories, ensuring consistent cleanup across the codebase.
• Maintenance Improvement: The removal of unused configuration lines contributes to a cleaner and more maintainable codebase, reducing potential for confusion or outdated directives.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request removes the unused PROJECT earthly-technologies/core directive from numerous Earthfiles across the repository. I've reviewed the changes and the full content of the modified files, and I can confirm that this directive was not being used for project-scoped secrets or any other feature in these files. This is a good cleanup that improves code clarity by removing unnecessary configuration. The changes are correct and I approve them.