Change Details

We don't use `printf()` in most other files, instead opting for `fprintf(stdout,...)`. Seeder code should follow the same pattern. Scripted diff using `sed -i -e 's/printf(\"/fprintf(stdout,\"/g' ./seeder/*` Depends on D4216

Using `fprintf()` allows us more control over where text is output to. This is especially relevant if we wish to change some of the output to a log file or stderr rather than the current behavior of outputting solely to stdout. It also better clarifies where the text is being output to making the code easier. Scripted diff using `sed -i -e 's/printf(\"/fprintf(stdout,\"/g' ./seeder/*`

We don't use `printf()` in most other files, instead opting for `fprintf(stdout,...)`Using `fprintf()` allows us more control over where text is output to. This is especially relevant if we wish to change some of the output to a log file or stderr rather than the current behavior of outputting solely to stdout. Seeder code should followIt also better clarifies where the text is being output to making the same patterncode easier. Scripted diff using `sed -i -e 's/printf(\"/fprintf(stdout,\"/g' ./seeder/*` Depends on D4216