chore: ignore warning in prod

[cmwylie19]

Description

Ignores the warning if you are in prod, it only allows the warning in dev mode. npx pepr dev

This means you don't get the warning in the controller, or through npx pepr init|build|format

process.on('warning') won’t directly suppress the warning because it only listens to the warnings after they have been emitted.

End to End Test:
(See Pepr Excellent Examples)

Related Issue

Fixes #1147

Relates to #

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Other (security config, docs update, etc)

Checklist before merging

• Unit, Journey, E2E Tests, docs, adr added or updated as needed
• Contributor Guide Steps followed

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.87%. Comparing base (d947861) to head (74bca7f).
Report is 29 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1152      +/-   ##
==========================================
- Coverage   86.71%   85.87%   -0.84%     
==========================================
  Files          26       27       +1     
  Lines        1076     1126      +50     
  Branches      230      231       +1     
==========================================
+ Hits          933      967      +34     
- Misses        132      157      +25     
+ Partials       11        2       -9     

see 6 files with indirect coverage changes

[btlghrants]

Just leaving a note that we reviewed in person -- LGTM.