docs: Document the process for merging pull requests

[ximinez]

DRAFT

I made a first pass at this before I injured my hand. I won't be contributing or updating for a bit. This draft is so folks can start leaving feedback while I'm out.

High Level Overview of Change

Context of Change

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactor (non-breaking change that only restructures code)
• Performance (increase or change in throughput and/or latency)
• Tests (you added tests for code that already exists, or your new feature included in this PR)
• Documentation update
• Chore (no impact to binary, e.g. .gitignore, formatting, dropping support for older tooling)
• Release

API Impact

• Public API: New feature (new methods and/or new fields)
• Public API: Breaking change (in general, breaking changes should only impact the next api_version)
• libxrpl change (any change that may affect libxrpl or dependents of libxrpl)
• Peer protocol change (must be backward compatible or bump the peer protocol version)

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 70.9%. Comparing base (f650949) to head (bf7bfbe).

Additional details and impacted files

@@           Coverage Diff           @@
##           develop   #5010   +/-   ##
=======================================
  Coverage     70.9%   70.9%           
=======================================
  Files          796     796           
  Lines        66792   66792           
  Branches     10998   10996    -2     
=======================================
+ Hits         47377   47380    +3     
+ Misses       19415   19412    -3     

see 2 files with indirect coverage changes