[Compiler] Fix condition compiling

[SupunS]

Work towards #3769

Description

There were three issues:

1. Similar to if-statements, emit-statements also could be coming from the inherited interfaces. Thus, when compiling emit-statements, the proper elaboration must be used. (✅ Fixed)
2. If the inherited condition refers to an unqualified-type (e.g: event, emit Event()), then the global lookup fail for the concrete type when compiling this inherited condition. (✅ Fixed).
   • This is because the event is a local type definition for the interface. Concrete type doesn't have the access.\
   • The fix was to re-write the inherited emit to be type-qualified. i.e: emit Event() → emit Contract.Event()
3. Similar to events, if the inherited condition refers to a function/imported symbol that is not available to the concrete type (can happen if the interface calls A.foo() inside the condition and interface has an import to A. But the concrete type that inherits the same condition does not import A. Then A.foo cannot be found to the compiler.) (❌ Not fixed yet).
   • This is not needed for the FT, so we can merge the PR in the current state, and fix this third issue separately.
   • Created Fix inherited conditions compilation #3878

---

• Targeted PR against master branch
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work
• Code follows the standards mentioned here
• Updated relevant documentation
• Re-reviewed Files changed in the Github PR explorer
• Added appropriate labels

[github-actions]

Cadence Benchstat comparison

This branch with compared with the base branch onflow:feature/compiler commit e9dea7c
The command for i in {1..N}; do go test ./... -run=XXX -bench=. -benchmem -shuffle=on; done was used.
Bench tests were run a total of 7 times on each branch.

Collapsed results for better readability

[turbolent]

Nice!

Unfortunately I also don't have a better idea than type qualifying, I guess it's fine for now