Retain support for FUSE2 #112
Description
Since 3.0.0, libfuse has maintained co-existence between its previous API iteration (referred to as fuse or fuse2) and its new API iteration (known as fuse3). This also applies to its macOS counterpart, macFUSE, which does the same.
Given the recent push to migrate over to fuse3 in #99, many older systems - mainly those stuck with the fuse2 API implementation are no longer able to build and benefit from the project. Though the differences between the two implementations, as of the opening of this issue, are not too different, the question that still looms is whether upstream would like to continue maintaining support for an otherwise functional, yet deprecated, fuse2 implementation.
Nevertheless, this could still be useful for the otherwise "weird" cases, yet highlights the strict fuse3 requirement being moot; this requires input and further discussion before any effort is put forth, hence this issue.