fix(core): Correctly detect Android Tauri configuration file, closes #7785

[i-c-b]

What kind of change does this PR introduce?

• Bugfix
• Feature
• Docs
• New Binding issue #___
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change?

• Yes, and the changes were approved in issue [bug] Tauri configuration file for Android is not detected on Linux #7785
• No

Checklist

• When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
• A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
• I have added a convincing reason for adding this feature, if necessary

Other information

[i-c-b]

By no means complete, the issue persists. I've tried --target, and the CARGO_BUILD_TARGET environment variable but it seems to do nothing to get the detection to pick up Android instead of Linux. To avoid a major refactor effort, I'd like to get some expert ideas from the core contributors to mobile support.

[amrbashir]

the TAURI CLI knows what target it will build, so you can just add a parameter to this method or a new method that takes that target and parses it.

[lucasfernog]

@i-c-b thank you for catching this issue! I pushed a small change to detect the target (using cfg!() macros only pulls the target we used to build the CLI, instead of the target we're compiling, so it needed a breaking change anyway).

[amrbashir]

oh boy that's a lot cleaner