Fix type checker error with miniupnpc import (libp2p#1010)

- Add type ignore comment for miniupnpc import
- Resolves import-untyped error in type checker
- Fixes make pr command failure

Quick Fix for libp2p#1009

Author: acul71

README.md

@@ -138,4 +138,4 @@ _(non-normative, useful for team notes, not a reference)_
 
 **Communication over one connection with multiple protocols**: X and Y can communicate over the same connection using different protocols and the multiplexer will appropriately route messages for a given protocol to a particular handler function for that protocol, which allows for each host to handle different protocols with separate functions. Furthermore, we can use multiple streams for a given protocol that allow for the same protocol and same underlying connection to be used for communication about separate topics between nodes X and Y.
 
-**Why use multiple streams?**: The purpose of using the same connection for multiple streams to communicate over is to avoid the overhead of having multiple connections between X and Y. In order for X and Y to differentiate between messages on different streams and different protocols, a multiplexer is used to encode the messages when a message will be sent and decode a message when a message is received. The multiplexer encodes the message by adding a header to the beginning of any message to be sent that contains the stream id (along with some other info). Then, the message is sent across the raw connection and the receiving host will use its multiplexer to decode the message, i.e. determine which stream id the message should be routed to.
+**Why use multiple streams?**: The purpose of using the same connection for multiple streams to communicate over is to avoid the overhead of having multiple connections between X and Y. In order for X and Y to differentiate between messages on different streams and different protocols, a multiplexer is used to encode the messages when a message will be sent and decode a message when a message is received. The multiplexer encodes the message by adding a header to the beginning of any message to be sent that contains the stream id (along with some other info). Then, the message is sent across the raw connection and the receiving host will use its multiplexer to decode the message, i.e. determine which stream id the message should be routed to.

libp2p/discovery/upnp/upnp.py

@@ -1,7 +1,7 @@
 import ipaddress
 import logging
 
-import miniupnpc
+import miniupnpc  # type: ignore[import-untyped]
 import trio
 
 logger = logging.getLogger("libp2p.discovery.upnp")

newsfragments/1009.bugfix.rst

@@ -0,0 +1 @@
+Fix type checker error with miniupnpc import by adding type ignore comment.