[Feature] Generate 3DS QR codes for installing games on a console over the network

[idio-sync]

Is your feature request related to a problem? Please describe.
Not a problem, just an idea.

Describe the solution you'd like
When a .cia file in the 3ds platform category is scanned in to the database, romm could generate a QR code to display on that game's page that could be scanned by the 3DS camera (using the fbi app) to install that game. Retronas does it kinda this way with a script that outputs codes to a directory served by html (https://github.com/retronas/retronas/wiki/3DS-QR-codes). Since romm is serving the .cia files for download over http anyway, all that is needed is a qr code to be generated with the link that romm creates and then that code needs to be added to the game's page somewhere.

Describe alternatives you've considered
This can be done manually (see below) but an automated approach shouldn't be anywhere near impossible.

Additional context
When I posted this idea on discord, danblu3 tested it by manually generating a qr code with romm's url to the file and then scanning that qr with a 3DS using the fbi app. He was able to install the file no problem over his lan from romm, so we know that aspect already works. He placed the qr image in the notes section, which is an elegant workaround and not at all outside of the existing framework.

Ideally, though, it would be placed somewhere immediately visable on the page, maybe in the empty space to the right of the file/version/info or underneath the box art. The qr would be linked to that .cia file specifically based on the download link romm creates, so multiple versions/dlc/updates wouldn't be an immediate issue if the user's library is set up with a game and it's related .cia files not in the "multidisc" configuration, instead using the dropdown box to select which .cia they would like.

Also, Python already has a library “qrcode” for generating QR code images, which would make the qr code generation aspect possible. Output paths based on inputs could be specified, so the resulting qr image can be put in the resources folder alongside the big/small cover and then pulled to be shown on the page. Basically, most of the underlying bits are already there, it just needs to be put together in a cohesive way. I barely know code, though, so I'm not sure how much work/how hard that would actually be.