Add native function declarations for all relevant Test contract functions

[m-Peter]

Closes #2822

Description

With the introduction of #2821, we can now declare native functions inside the Test contract, and remove the workaround that used CompositeType.ResolveMembers().

---

• 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

[m-Peter]

I am still getting some checking errors for native function declarations with type parameters, e.g.:

panic: Checking failed:
error: cannot find type in this scope: `T`
   --> Test:445:50

The relevant function declaration is:

/// Creates a matcher with a test function.
/// The test function is of type '((T): Bool)',
/// where 'T' is bound to 'AnyStruct'.
///
access(all)
native fun newMatcher<T: AnyStruct>(_ test: ((T): Bool)): Test.Matcher {}

To my knowledge, I have updated all the relevant parser.Config & sema.Config usages:

parser.Config{
	NativeModifierEnabled: true,
	TypeParametersEnabled: true,
}

&sema.Config{
	BaseValueActivation:     activation,
	AccessCheckMode:         sema.AccessCheckModeStrict,
	AllowNativeDeclarations: true,
}

What could be the root cause of this checking error? 🤔

[SupunS]

Can you maybe rebase the PR on top of #2850, and see if this is now solved?

[m-Peter]

Hey @SupunS,

I have rebased on top of master, and indeed the checking error regarding type parameters is solved. However, I hit another roadblock in this commit 6eb4de7. Basically, we have two functions with arity (Test.assert & Test.fail):

// `message` parameter is optional
Arity: &sema.Arity{Min: 1, Max: 2},

Which is not possible to somehow define with native declarations. Any suggestions on how to work around this? Maybe change the function interface?
Related discord thread: https://discord.com/channels/613813861610684416/1159499730573860895/1159806153862172712

[m-Peter]

Closing this in favor of #2926