[eas-cli] Further no longer require owner field for SDK >= 53 or canary #3017
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

Why
Part 2 of #2835. Missed some cases in that one.
Essentially the
usernamefield is supplied in EAS build jobs and in the build metadata. It is only used for an environment variable which is known to be undefined for robots: https://docs.expo.dev/eas/environment-variables/#:~:text=learn%20more)-,EAS_BUILD_USERNAME,-%3A%20the%20username%20ofHow
This makes two changes:
eas inithas not yet been run (projectId is not yet set) and a robot is running the command.getUsername(used by build and build metadata). Previously this function was responsible for preventing a prebuild error it seems. This PR updates it to just get the username or return undefined for robots.Test Plan
Run
neas buildas a robot with a project that has a eas project ID is SDK 53 and see it no longer throws an error.