Remove InterceptableAttribute

[RikkiGibson]

Test plan: #67421
Removing InterceptableAttribute per discussion in #67970.

5cd9e59 and 88bd1a0 are mechanical changes so should be more skimmable.

[RikkiGibson]

This is testing something different than before the PR. The scenario just came to my mind while working on it and rather than moving to test plan and doing it later I decided to get it done now.

[jcouv]

The location of the call is the location of the simple name syntax which denotes the interceptable method. For example, in app.MapGet(...), the name syntax for MapGet would be considered the location of the call. For a static method call like System.Console.WriteLine(...), the name syntax for WriteLine is the location of the call. If we allow intercepting calls to property accessors in the future (e.g obj.Property), we would also be able to use the name syntax in this way.

What does "interceptable method" mean now? (if we decide to remove usages of that term, there's a few more below)

---

Refers to: docs/features/interceptors.md:82 in ac5cb24. [](commit_id = ac5cb24, deletion_comment = False)

[jcouv]

LGTM Thanks (iteration 4) modulo a spec/doc question

[RikkiGibson]

I think we just want distinctive terms for "the method that gets intercepted" and "the method that is intercepting".