Introduce FenceCycle Chaining

If we want to allow submitting multiple pieces of work to the GPU at once while still requiring CPU synchronization, we'll need to track all past fence cycles associated with a resource alongside the current one. To solve this the concept of chaining fences has been introduced, fences from past usages can be chained to the latest fence which'll then recursively forward operations to chained fences.

This change also ends up mandating a move away from `FenceCycleDependency` as it would prevent fences from concurrently locking the same resources which is required for chaining to work as two fences being chained fundamentally means they're locking the same resources. The `AtomicForwardList` is therefore used as the new container.

app/src/main/cpp/skyline/gpu/buffer.h

@@ -20,7 +20,7 @@ namespace skyline::gpu {
      * @brief A buffer which is backed by host constructs while being synchronized with the underlying guest buffer
      * @note This class conforms to the Lockable and BasicLockable C++ named requirements
      */
-    class Buffer : public std::enable_shared_from_this<Buffer>, public FenceCycleDependency {
+    class Buffer : public std::enable_shared_from_this<Buffer> {
       private:
         GPU &gpu;
         std::mutex mutex; //!< Synchronizes any mutations to the buffer or its backing
@@ -93,7 +93,7 @@ namespace skyline::gpu {
          * @brief A delegate for a strong reference to a Buffer by a BufferView which can be changed to another Buffer transparently
          * @note This class conforms to the Lockable and BasicLockable C++ named requirements
          */
-        struct BufferDelegate : public FenceCycleDependency {
+        struct BufferDelegate {
             std::shared_ptr<Buffer> buffer;
             const Buffer::BufferViewStorage *view;
             std::function<void(const BufferViewStorage &, const std::shared_ptr<Buffer> &)> usageCallback;