eas update should allow using env from eas build profile

### Do you understand that any feature requests opened in this repository will be closed?

Yes

### Background

I have an app using fingerprints to decide when a change should trigger a full native build or just an update.
The fingerprint is generated using `eas-cli fingerprint:generate --build-profile ${profile}‘. It automatically reads the correct env vars from `eas.json` (e.g. `EXPO_PUBLIC_API_BASE_URL` or `EXPO_PUBLIC_APP_VARIANT`).
The fingerprint matches the one of the build from `eas build --profile ${profile}` as expected.

But `eas update` though does not support reading environment variables from `eas.json` which means the fingerprint of the update does not match the build or fingerprint:generate if the environment variables aren‘t set explicitly to mirror the values from `eas.json`.

### Enhancement

`eas update` should support eas build profiles so fingerprints generated by that update match the builds from `eas build` for the given profile.
This ensures that the update can be delivered while using the fingeprint runtimeVersion policy.