fix(android): Fall back to compiled_item ref ID for AAB resource resolution

[runningcode]

Summary

• When an AAB manifest attribute has a value string like @string/app_name_bootstrap that doesn't match any entry in the protobuf resource table, the code now falls back to resolving via the compiled_item.ref.id instead of returning None.
• This fixes apps where the manifest label references a resource name that doesn't exist in resources.pb, but the numeric resource ID in compiled_item.ref.id resolves correctly.

Root Cause

In _get_optional_attr_value(), when attribute.value starts with @, it calls get_value_by_key() for a name-based lookup and directly returns the result — even if None. It never tries the compiled_item.ref.id path which resolves by numeric resource ID.

Production logs for a failing artifact:

optionalAttrValueWithFallback: label, 1010001
could not find attribute matching filter
could not find attribute by name, trying to find by resourceId
No entry found with the name @string/app_name_bootstrap.

The resource ID-based lookup would have succeeded, but was never attempted.

Fixes EME-900

[linear]

EME-900 App name showing up as "Unknown" for Android Builds

[chromy]

I don't think the getattr is right here. The generated interface (Resources_pb2.pyi) implies it will always exist as a field on the object.

I think the right thing is either:

compiled_item = attribute.compiled_item if attribute.HasField("compiled_item") else None

If we need to handle this being unset, or:

compiled_item = attribute.compiled_item

if not.

• launchpad/src/launchpad/artifacts/android/resources/protos/Resources_pb2.pyi

  Line 803 in 56cf356

  compiled_item: Item

• https://protobuf.dev/reference/python/python-generated/#embedded_message

[chromy]

lgtm % one comment