chore: updated pull-request workflow to build debug APK

[AsCress]

I guess we should follow the same procedure that we do for the native app. Build debug APKs on pull requests and release APKs and bundles on push-events.
Currently, we are building release APKs on pull requests, which can't be installed on devices since we aren't signing them, and hence can't be tested by contributors.

Screenshots / Recordings

N/A

Checklist:

• No hard coding: I have used resources from strings.xml, dimens.xml and colors.xml without hard coding any value.
• No end of file edits: No modifications done at end of resource files strings.xml, dimens.xml or colors.xml.
• Code reformatting: I have reformatted code and fixed indentation in every file included in this pull request.
• No extra space: My code does not contain any extra lines or extra spaces than the ones that are necessary.

Summary by Sourcery

Build debug APKs instead of release APKs for pull requests to allow testing on contributor devices.

Enhancements:

• Store only the debug APK as an artifact.

CI:

• Build debug APKs in the Android build workflow.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the Android build workflow to generate debug APKs instead of release APKs. This allows contributors to test the app on their devices without signing the APK.

Sequence diagram for updated Android build workflow on pull requests

sequenceDiagram
    participant PR as Pull Request
    participant GH as GitHub Actions
    participant FB as Flutter Build
    participant A as Artifacts

    PR->>GH: Trigger workflow
    GH->>FB: Build debug APK
    Note over FB: --debug flag added
    FB-->>GH: Generate debug APK
    GH->>A: Upload APK artifact
    Note over A: Only debug APK stored

Loading

File-Level Changes

Change	Details	Files
Build debug APKs instead of release APKs	Removed the release APK and appbundle build steps. Added a debug APK build step. Updated the upload artifact step to only store the debug APK file	.github/actions/android/action.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @AsCress - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[github-actions]

Build successful. APKs to test: https://github.com/fossasia/pslab-android/actions/runs/12643222922/artifacts/2393302386