Derive runtime package names dynamically

[vibhor1102]

Summary

• derive package-sensitive runtime targets from the installed app package instead of hardcoding com.buzbuz.smartautoclicker
• fix tutorial launch, notification settings routing, and notification action broadcast names for builds where the package name differs from vanilla
• keep the change narrow and behavior-preserving for normal builds while improving support for obscured or otherwise renamed package variants

Why

This is meant to solve a possible issue with the obscured version and any other package name modifications.

In my personal fork with a modified package name, hardcoded app package usage caused crashes. The most noticeable case was opening the tutorial, which led to an instant crash because the app tried to start a component under the vanilla package name.

More generally, avoiding hardcoded app package names in these runtime paths is good hygiene and makes the app more robust to package renaming.

Fixes #925

Testing

• hosted fork debug APK workflow passed for the equivalent patch on my fork
• the resulting patched debug APK installed successfully on device after replacing an older debug install
• this exact upstream branch/version has not been manually tested by me on device yet