erlang_ls unable to reference include_lib library properly when the root Erlang project is not at the root of the opened folder

[mononym]

For reasons I won't get too deep into, it's the way my job has things set up so I can't do much about it, I have a situation where I have an Erlang app that is nested a couple levels deep in a git repo. For example: account/service/accountserver

Where account is the git repo and contains a bunch of things around deployments and so on. Inside service/accountserver is where the actual folder for the Erlang app is, containing the rebar.config and all that.

If I open the inner folder, the one containing the actual Erlang project accountserver, erlang_ls is able to properly find the includes. I use the following config for that folder:

apps_dirs:
  - "_build/default/lib/*"
include_dirs:
  - "_build/default/lib/*/include"
  - "include"

However, if I instead open VSC from the repo root, that outer account folder, the included libraries cannot be found. I have tried all of the following combinations of paths to get it to work:

apps_dirs:
  - "/Users/me/git/account/service/accountserver/_build/default/lib/*"
  - "service/accountserver/_build/default/lib/*"
  - "_build/default/lib/*"
include_dirs:
  - "/Users/me/git/account/service/accountserver/_build/default/lib/*/include"
  - "/Users/me/git/account/service/accountserver/include"
  - "service/accountserver/_build/default/lib/*/include"
  - "service/accountserver/include"
  - "_build/default/lib/*/include"
  - "include"

Ideally, I would like to be able to open from that outer folder so VSC can latch onto the git repo and track all the changes for me. The linking of includes works from that inner folder, but I lose all the version control QOL things that I have access to from the IDE, including indicators of what lines have changed and so on.

I don't see a config option to tell erlang_ls to look in a different directory for the Erlang project root like the elixir_ls has with the option elixirLS.projectDir. Is there any way to make this work as is? Would this work with a new configuration option to tell erlang_ls where the real root directory is that could be searched/prepended?