Semantic highlighting marking a class usage as a constant

Ruby version

3.2.2

Code snippet

This may not be the most lightweight way to reproduce it, but it's visible.

# Use Alpine as the base image
FROM alpine:latest

# Set the working directory
WORKDIR /root

# Install necessary packages
RUN apk add --no-cache \
  git \
  curl \
  build-base \
  zlib-dev \
  openssl-dev \
  readline-dev \
  linux-headers \
  libffi-dev \
  cmake \
  automake \
  autoconf \
  libtool \
  pkgconf \
  gettext-tiny-dev \
  ruby \
  ruby-dev \
  bash \
  yaml-dev

# Clone and build Neovim from source
RUN git clone https://github.com/neovim/neovim.git && \
  cd neovim && \
  make CMAKE_BUILD_TYPE=Release && \
  make install

# Clone the LazyVim starter repository
RUN git clone https://github.com/LazyVim/starter ~/.config/nvim

# Copy the content of custom_plugins.lua from an external file
COPY custom_plugins.lua /root/.config/nvim/lua/plugins/custom_plugins.lua

# Create example.rb inline
RUN echo -e "class Foo\n  def self.bar\n    Foo.new # `Foo` should be the same color in both lines\n  end\nend" > ~/example.rb

# Create Gemfile inline
RUN echo "source 'https://rubygems.org'" > ~/Gemfile

# Install bundler and gems specified in the Gemfile
RUN gem install bundler && \
  bundle install

# Start Neovim headlessly and install plugins
RUN nvim -es -u ~/.config/nvim/init.lua -i NONE -c "Lazy" -c "qa"

# Start a shell when the Docker container is run
CMD ["sh"]

-- store this in the same folder of the Dockerfile as `custom_plugins.lua`
return {
    {
        "williamboman/mason.nvim",
        opts = function(_, opts)
            vim.list_extend(opts.ensure_installed, {
                "ruby-lsp",
            })
        end,
    },
    {
        "neovim/nvim-lspconfig",
        opts = {
            servers = {
                ruby_ls = {},
            },
        },
    },
}

Run:

docker build -t example .
docker run -ti example
# inside
nvim example.rb

Wait a bit and you'll see some notifications like installing ruby_ls, ruby_ls installed, and some seconds later the server will be started automatically. At that point you'll see the color of the second Foo change.

Description

I wanted to replace solargraph with ruby_ls with neovim (and LazyVim). When switching I noticed that the highlighting was different. I've noticed that this is most probably because ruby_ls semantic highlighting.

I'm using https://github.com/maxmx03/solarized.nvim with neo theme, although I can reproduce it with other themes.
After using :Inspect, i've noticed the following

Foo here is highlighted as a a namespace / constant, where on declaration it's as a class:

Expected output

I would expect that in both cases Foo is the same color (orange, as a Type)

Reproduce the issue with example.rb after ruby_ls starts, using the Dockerfile setup and the :Inspect command to compare the Foo declaration and usage. Trace the semantic-highlighting entry point for Ruby class references; done means both occurrences are classified and rendered consistently as a type, with a regression check for this example.