Enable BuildConfig generation for memory-vault debug build

[Copilot]

The debug APK build fails while configuring :memory-vault because custom BuildConfig fields are defined but BuildConfig generation is disabled. This change enables BuildConfig generation so assembleDebug can proceed.

• Build configuration
  • Enable BuildConfig generation in memory-vault to match existing buildConfigField usage.

Example:

android {
    buildFeatures {
        buildConfig = true
    }
}

Original prompt

fix the debug workflow build and test it before handing it to me : Run ./gradlew assembleDebug --no-daemon
Downloading https://services.gradle.org/distributions/gradle-8.13-bin.zip
.............10%.............20%.............30%.............40%.............50%.............60%.............70%.............80%.............90%.............100%

Welcome to Gradle 8.13!

Here are the highlights of this release:

• Daemon JVM auto-provisioning
• Enhancements for Scala plugin and JUnit testing
• Improvements for build authors and plugin developers

For more details see https://docs.gradle.org/8.13/release-notes.html

To honour the JVM settings for this build a single-use Daemon process will be forked. For more on this, please refer to https://docs.gradle.org/8.13/userguide/gradle_daemon.html#sec:disabling_the_daemon in the Gradle documentation.
Daemon will be stopped at the end of the build
Calculating task graph as no cached configuration is available for tasks: assembleDebug

FAILURE: Build failed with an exception.

• What went wrong:
  A problem occurred configuring project ':memory-vault'.

                defaultConfig contains custom BuildConfig fields, but the feature is disabled.

                  To enable the feature, add the following to your module-level build.gradle:

android.buildFeatures.buildConfig = true

• Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
Get more help at https://help.gradle.org.

BUILD FAILED in 1m 5s
Configuration cache entry stored.
Error: Process completed with exit code 1.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Copilot]

Pull request overview

This PR fixes a build configuration issue in the memory-vault module where BuildConfig generation was disabled despite having custom BuildConfig fields defined, causing the debug APK build to fail during configuration.

Changes:

• Enabled BuildConfig generation in the memory-vault module's build configuration

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.