feat: Add Benchmark App & No-Op Features

[jshlbrd]

Description

• Adds a development app for benchmarking
  • Adds noop (no-op, no operation) transform and sink for enabling zero data processing
  • Updates gitignore for profiling binaries generated by benchmark app
• Refactors stdout sink to return an empty struct

Motivation and Context

The no-op features are helpful for development and integration testing (e.g., deploy a Substation node that doesn't output data but still processes it), and the benchmark app provides an easy way to do application-level performance tests. Here are some examples:

256 MB memory, 1 CPU

$ ./cmd/development/benchmark/benchmark -config examples/quickstart/config.json -input examples/quickstart/data.json 
100000 events in 7.571924086s (13206.68 events/sec)
1 MB in 7.571924086s (0.16 MB/sec)

1 GB memory, 2 CPU

$ ./cmd/development/benchmark/benchmark -config examples/quickstart/config.json -input examples/quickstart/data.json 
100000 events in 865.146917ms (115587.30 events/sec)
1 MB in 865.146917ms (1.43 MB/sec)

2 GB memory, 4 CPU

$ ./cmd/development/benchmark/benchmark -config examples/quickstart/config.json -input examples/quickstart/data.json 
100000 events in 947.320584ms (105560.89 events/sec)
1 MB in 947.320584ms (1.31 MB/sec)

How Has This Been Tested?

Tested locally, no new unit tests required.

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• [x] My code follows the code style of this project.
• [x] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.