🐛 Rome invalid catch of object key name outside of defined interface scope

[MrSimmmons]

Environment information

CLI:
  Version:                      12.1.2
  Color support:                true

Platform:
  CPU Architecture:             x86_64
  OS:                           macos

Environment:
  ROME_LOG_DIR:                 unset
  NO_COLOR:                     unset
  TERM:                         "xterm-256color"
  JS_RUNTIME_VERSION:           "v14.18.1"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "yarn/1.22.19"

Rome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    true
  VCS disabled:                 true

Workspace:
  Open Documents:               0

What happened?

See playground for example

Notice how in the playground example you can rename the second key to any other string and it works fine.

Expected result

I should be able to re-declare an interface object key in a different scope using the same name without Rome triggering an error

Code of Conduct

• I agree to follow Rome's Code of Conduct

[MrSimmmons]

Please feel free to rename the title. I'm unsure how to describe the issue in a small amount of words

[ematipico]

Duplicate of #4478