[Tapioca Add-on] Trigger DSL generation upon file changes

[KaanOzkan]

Motivation

Merge part of tapioca add-on logic

Implementation

• Bump ruby-lsp and ruby-lsp-rails
• Use new API in ruby-lsp
• Implement workspace_did_change_watched_files method that uses the Ruby LSP index to find potentially modified constants in a file and sends them to the Rails app

Tests

We'll add tests when we can test rails client

[KaanOzkan]

Using grep, getting subclasses and then filtering them out feels weird to me. Wdyt of an API like this where you have a rest arg and use == instead? Or making the second argument optional and returning all entries by default?

[vinistock]

You can just use the parent class to filter both at the same time.

Suggested change

	entries = T.must(@index).entries_for(path, RubyIndexer::Entry::Class, RubyIndexer::Entry::Module)
	entries = T.must(@index).entries_for(path, RubyIndexer::Entry::Namespace)

[KaanOzkan]

I can't only use the parent class because it includes singleton classes. So I'm trying to avoid this filtering with a different API in Ruby LSP main...andyw8/tapioca-lsp#diff-8243d0258619c7955b4277251f121d4b6788da80bcae39fe5130f27019d143bbR64

[KaanOzkan]

I think for our use case being able to omit the types and do our own filtering in tapioca makes sense. Will you accept that change in Ruby LSP?

[vinistock]

I mean, we created that API for the Tapioca add-on, so we can change it to whatever makes sense.

[vinistock]

You can just use the parent class to filter both at the same time.

Suggested change

	entries = T.must(@index).entries_for(path, RubyIndexer::Entry::Class, RubyIndexer::Entry::Module)
	entries = T.must(@index).entries_for(path, RubyIndexer::Entry::Namespace)

[vinistock]

We need to also update the Addon.get call to constraint the version to one that defines the new APIs:

# We need to change this to >= 0.3.18
addon = T.cast(::RubyLsp::Addon.get("Ruby LSP Rails", ">= 0.3.17", "< 0.4"), ::RubyLsp::Rails::Addon)