Benchmark cleanup

[roji]

This PR cleans up some benchmark stuff.

@sebastienros once this is merged, we'd need the corresponding cleanup to also occur in the database. I hope you can help us with that...

Benchmark name changes:

• InitializationSqliteTests -> Initialization
• FuncletizationSqliteTests -> Funcletization
• NavigationsQuerySqliteTests -> NavigationsQuery (does not appear in dashboard!)
• QueryCompilationSqliteTests -> QueryCompilation (does not appear in dashboard!)
• RawSqlQuerySqliteTests -> RawSqlQuery
• SimpleQuerySqliteTests -> SimpleQuery

For the following, I've configured BDN to always show the times for exactly one operation, even when the benchmark internally executes a loop. That means we'd need to multiply historical values in the database:

• AddDataVariations: multiply by 20000
• ExistingDataVariations: multiply by 20000
• ChildVariations: multiply by 10000
• ParentVariations: multiply by 5000
• InitializationTests.CreateAndDisposeUnusedContext: multiply by 10000
• InitializationTests.InitializeAndQuery_AdventureWorks: multiply by 1000
• InitializationTests.InitializeAndSaveChanges_AdventureWorks: multiply by 100
• FuncletizationTests: multiply by 100
• NavigationsQueryTests: multiply by 10
• QueryCompilation: multiply by 10

[smitpatel]

I don't think OperationsPerInvoke is correct thing for all of them. Bring it to design meeting please.

[roji]

OK we've discussed this in design and agreed it's a good direction.

@sebastienros, this now depends on you :) When we merge this, all the above changes will need to take place in the database - will you be able to help us with this?

[smitpatel]

Ping!

[sebastienros]

Not yet ready to do it. But this will be done.

[roji]

Closing for age, will re-tackle this again in the future. Tracking issues are #25361 and #19874.