CI: Remove daily benchmarks pipeline

[martintomazic]

Closes #6486.

Daily benchmark have been failing for a while: https://buildkite.com/oasisprotocol

They weren't used for 1 year+, neither are metrics and their regression from light e2e tests representative therefore we can safely remove them.

Lets open a new issue instead for creating a new pipeline that triggers on the new oasis-core release and starts a representative load (e.g. sync from latest checkpoint or few months back in time) and check performance regression + store relevant artifacts long time.

[netlify]

✅ Deploy Preview for oasisprotocol-oasis-core canceled.

Name	Link
🔨 Latest commit	c45a76b
🔍 Latest deploy log	https://app.netlify.com/projects/oasisprotocol-oasis-core/deploys/69e09beab6cb0b00085f67b1

[martintomazic]

Long test seems to work:

• https://buildkite.com/oasisprotocol/oasis-core-long-tests

Daily benchmarks seems to be stuck at reading non-existing stuff, likely a config/pipeline issue (exploring):

• https://buildkite.com/oasisprotocol/oasis-core-daily-benchmarks/builds/940

[martintomazic]

Once merged also Archive Pipeline in the buildkite UI?

[peternose]

I would add internal changelog, so that it is easier to find these changes and the removed code.

[martintomazic]

I would add internal changelog, so that it is easier to find these changes and the removed code.

I see your point, but looking at changelog descriptions, the intended audience are not people working on the code itself so CI changes should not be part of it.

Opened an issue to track this: #6503.

If you are fine I will merge as is?

[peternose]

I would add internal changelog, so that it is easier to find these changes and the removed code.

I see your point, but looking at changelog descriptions, the intended audience are not people working on the code itself so CI changes should not be part of it.

Opened an issue to track this: #6503.

If you are fine I will merge as is?

Internal is still for us, I think. Yes, you can merge.