Is your feature request related to a problem? Please describe.
Full integration with Drive UX removes obstacles to usage in various scenarios (e.g., #14).

Describe the solution you'd like
The file referenced by the shortcut is used as the Drive file in sync ops, if possible. The plugin should recognize shortcuts as a simple file indirection. Plugin (and common sense) rules still apply: the shortcut corresponding to the database file must be uniquely named among all shortcuts and files on Drive (if not using Target Folder), or in the specified the Target Folder (if using the Target Folder feature). Shortcuts are never created by the plugin. Shortcuts referencing zombie files (deleted files or files in Trash) are not valid as plugin targets, and should produce reasonable errors in sync ops.

In the case of a shortcut and file of the same name existing in the target location, the plugin should, at the user's option,

• Quietly choose the file for the current operation, and ignore the shortcut, or..
• Abandon the operation and display an informative error message.

Describe alternatives you've considered
Ignore shortcuts (current behavior), and fix possible errors witnessed in #14.

Additional context
The "shortcut" mechanism mentioned above does not refer to the somewhat nebulous feature of "external" or "third-party" shortcuts.

See Also:
Find files & folders with Google Drive shortcuts (support.google.com).
Create pointers to any file or folder in Google Drive with shortcuts (Google Workspace)