Relax strictness of annotation RBI files

[paracycle]

Type of Change

• Add RBI for a new gem
• Modify RBI for an existing gem
• Other:

Changes

I changed all the annotation files to typed: true since anything above that is useless for annotation RBI files for two reasons:

1. There is nothing the end-user can do if the annotation RBI file has errors at the higher strictness levels. It causes confusion, and makes end-users override the strictness in their config to work around it. This is related to Replace Class with T::Class[T.anything] in lhm-shopify RBI #168
2. As per my comment in #168, as of today, Sorbet does not error for methods missing signatures in RBI files that are at typed: strict or above. That means that we hadn't been enforcing signatures to exist until now anyway.

So the changes I've made can be read commit by commit and are:

1. Change all annotation RBI file strictness levels to be typed: true and force it to be so for all RBI files via the rubocop check.
2. Use the Sorbet/EnforceSignatures cop to error for any methods that don't have signatures
3. Fix existing errors related to methods and missing signatures