--exclude-untyped option does not exclude the untyped constants

[tk0miya]

Describe the bug
sord generates untyped definitions for constants even if --exclude-untyped option given.

To Reproduce

This is a minimal reproducible example.

# app/app.rb
class Foo
  CONST = 1
end

Expected behavior

I think they should be suppressed.

Actual behavior

I ran the following command:

$ bundle exec sord --rbs --exclude-untyped --no-sord-comments sig/sord.rbs  
[INFO ] Running YARD...
Files:           1
Modules:         0 (    0 undocumented)
Classes:         1 (    1 undocumented)
Constants:       1 (    1 undocumented)
Attributes:      0 (    0 undocumented)
Methods:         0 (    0 undocumented)
 0.00% documented
[OMIT ] (Foo::CONST) no YARD return type given, using untyped
[DONE ] Processed 1 objects (1 namespaces and 0 methods)  

Result:

class Foo
  CONST: untyped
end

Additional information

The latest version of rbs prototype rb command tries to analyze the type of constants statically and generates them as possible. So it's very helpful if sord does not generate the untyped constants. Then I'll be able to merge the result of these commands.