Allow use of multiple ENet channels

[cgutman]

Description

ENet channels provide a solution to the head-of-line blocking issue common to reliable protocols after a packet loss. I'm adding multi-channel support to moonlight-common-c to be able to send mouse/keyboard/gamepad on separate channels, but we need to accept more than one channel for it to work.

This is a trivial change to pass 0 instead of 1 as the channelLimit parameter.

Screenshot

Issues Fixed or Closed

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)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

Branch Updates

LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.

• I want maintainers to keep my branch updated