Unexpected `textDocument/references` results on keys inside nested tables

Describe the bug
textDocument/references is returning unexpected results when used in a specific situation (more about that below).

To Reproduce

1. Paste the following snippet in a lua file

ENUM = {
  VALUE1 = 1,
  VALUE2 = 2,
}

a = {
  { type = ENUM.VALUE1 },
  { type = ENUM.VALUE1 },
  { type = ENUM.VALUE2 },
}

2. Move cursor over the 1st instance of "type" key in the a table
3. Request references (textDocument/references)
4. Observe the faulty results which comprise of the hovered "type" key + both instances of "VALUE1"

Expected behavior
Results that comprise of all 3 instances of "type" key

Additional context
textDocument/rename on the other hand only renames the hovered "type" key while expected to rename all 3 of its instances

Environment

• OS: Linux
• Client: Neovim

Reproduisez le problème dans un fichier Lua en utilisant l’exemple montré de table imbriquée et demandez textDocument/references sur la première clé de type. Comparez les emplacements renvoyés avec le comportement de textDocument/rename ; le travail est terminé lorsque les références incluent les trois clés de type sans inclure VALUE1 ni VALUE2.