Seperate sorbet sigs from rb files

[donaldong]

This separates the sorbet sigs from rb files so sorbet runtime won't affect the lib code.

Test Plan

• ci

[hdoan741]

You can extends T::Sig::WithoutRuntime to keep the sig in the same file as the file but skip the runtime checks.

[donaldong]

You can extends T::Sig::WithoutRuntime to keep the sig in the same file as the file but skip the runtime checks.

Actually, I think we're moving way from sorbet-runtime completely; and only use sorbet for static tc

[codecov]

Codecov Report

Merging #80 (2f3c00a) into master (aaa8550) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #80      +/-   ##
==========================================
+ Coverage   96.95%   96.97%   +0.01%     
==========================================
  Files          35       35              
  Lines        1743     1553     -190     
==========================================
- Hits         1690     1506     -184     
+ Misses         53       47       -6     

Impacted Files	Coverage Δ
lib/redcord/actions.rb	97.93% <ø> (+2.48%)	⬆️
lib/redcord/attribute.rb	98.46% <ø> (-0.35%)	⬇️
lib/redcord/base.rb	100.00% <ø> (ø)
lib/redcord/lua_script_reader.rb	100.00% <ø> (ø)
lib/redcord/migration.rb	100.00% <ø> (ø)
lib/redcord/migration/index.rb	86.66% <ø> (ø)
lib/redcord/migration/ttl.rb	100.00% <ø> (ø)
lib/redcord/redis.rb	100.00% <ø> (ø)
lib/redcord/relation.rb	98.70% <ø> (-0.27%)	⬇️
lib/redcord/serializer.rb	100.00% <ø> (ø)
... and 6 more

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[mattxwang]

Note - to deal with the merge conflicts, I went through each merge file and moved T::sig changes to the private_rbi folder, trying to contextually understand what happened by looking at prior PRs. Think it's also now up to me to port over the rest of the changes to master.

[mattxwang]

Hey @donaldong, just wanted to ask - what was the original purpose of this PR / how should I continue it, if at all? Katy and I were considering also completely removing sorbet from the project.

Alternatively, I can port over the original remove-sig logic to the new code that were introduced to master since this PR was opened! If that's the case, should I be:

• removing all instances of sorbet in runtime code, including TypeCoerce, T::Struct, etc.?
• or, just removing sigs, but keeping general runtime code