Code analysis gives warning when catching on exception from other module

Consider the following example:

module Test = {
  exception Nested

  @raises(Nested)
  let raises = async () => raise(Nested)
}

let raises = async () =>
  try await Test.raises() catch {
  | Test.Nested => Js.log("Not found")
  }

it gives me:
raises might raise Nested (test.res:9:12) and is not annotated with @raises(Nested)

However, if I open Test instead:

module Test = {
  exception Nested

  @raises(Nested)
  let raises = async () => raise(Nested)
}

open Test

let raises = async () =>
  try await Test.raises() catch {
  | Nested => Js.log("Not found")
  }

Everything works fine

Issue transferred from (https://github.com/rescript-association/reanalyze/issues/188)

Reproduce the warning with the qualified Test.Nested example in test.res, then compare it with the open Test variant. Trace the code-analysis path that resolves qualified exceptions; done means the qualified catch no longer produces the incorrect @raises warning while the existing open form remains correct.