e2e tests: Rrmove extra schema creation

[aramikm]

Feature Description

Details

Currently we are creating schema for every e2e test that needs it. After seeding all DSNP schemas in all of our blockchain images, we don't need to create those schemas unless it is a schema related test.

Searched for Related Issues

• I have done a search for related issues and either found none, or noted them

[wilwade]

@aramikm Most are using getOrCreate functions from

frequency/e2e/scaffolding/helpers.ts

Line 538 in e95a823

export async function getOrCreateGraphChangeSchema(source: KeyringPair): Promise<u16> {

right?

I think the only one creating them is one that is testing the creation.

[aramikm]

We have a lot of ExtrinsicHelper.getOrCreateSchemaV3 usage with different schema names such as test.grantDelegation and ... for different pallets such as stateful pallet or other ones. These could get replaced with a well known schema such as the mentioned method and it would get rid of a lot of duplicated code and schema creation to tests other things