feat[tool]: delay global constraint check

[charles-cooper]

What I did

How I did it

How to verify it

Commit message

move the global constraint to later in compilation pipeline, so that you
can get a "partial compilation" of library modules with
`-f annotated_ast`. these library modules may declare `uses: X`, without
initializing `X`.

this is intended for third-party tools like IDEs, which may want to get
validation that a module will compile, even if it can't generate
bytecode (i.e., be a compilation target)

refactor:
* split `validate_semantics()` into `analyze_module()` and
  `validate_compilation_target()`

Description for the changelog

Cute Animal Picture

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 95.45455% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 85.07%. Comparing base (391f3cc) to head (7b239c9).

Files	Patch %	Lines
vyper/semantics/analysis/module.py	87.50%	0 Missing and 1 partial ⚠️

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #3810      +/-   ##
==========================================
- Coverage   85.18%   85.07%   -0.11%     
==========================================
  Files          92       92              
  Lines       13908    13914       +6     
  Branches     3116     3118       +2     
==========================================
- Hits        11847    11838       -9     
- Misses       1567     1581      +14     
- Partials      494      495       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[fubuloubu]

One strong suggestion

[fubuloubu]

why _r? seems like unexplained codebase definition to use these as external API, and _r should just be expanded

[charles-cooper]

_r is the convention for a lot of recursive functions. idk that it's really an external api, i can add a wrapper though