Moved internal.rb to be under the ruby_lsp directory

[Smittttty]

Motivation

PaymentService has an engine thats named Internal. With the latest version of ruby-lsp, PaymentService fails to load the Internal component. Related Buildkite.

586eccf was the only change that seemed like it could have caused this. Renaming the internal.rb file resolves the issue, as does moving the file to not be in the top-level /lib folder.

Implementation

Moved internal.rb to be under the ruby_lsp directory.

[st0012]

I think maybe the problem is that there shouldn't be any non-ruby-lsp.rb file located at the top-level /lib. Even if we changed it to requires.rb, it can still be loaded with require "requires", which may be some other gems' name. So the better solution to me is to place the internal.rb under the ruby-lsp namespace.

[paracycle]

Yeah 100% agreed with what @st0012 wrote above. We should be moving the require to inside the ruby-lsp folder.

[paracycle]

Thanks and sorry that this broke your workflow!

[Smittttty]

Thanks and sorry that this broke your workflow!

No problem, thanks for the quick review! ❤️