chore: restore SearchTransactionsResponse schema to specs

Author: linconvidal

api/src/main/resources/rosetta-specifications-1.4.15/api.yaml

@@ -2113,6 +2113,30 @@ components:
         success:
           type: boolean
           description: success is a synthetic condition populated by parsing network-specific operation statuses (using the mapping provided in `/network/options`).
+    SearchTransactionsResponse:
+      description: SearchTransactionsResponse contains an ordered collection of BlockTransactions that match the query in SearchTransactionsRequest. These BlockTransactions are sorted from most recent block to oldest block.
+      type: object
+      required:
+        - transactions
+        - total_count
+      properties:
+        transactions:
+          type: array
+          description: transactions is an array of BlockTransactions sorted by most recent BlockIdentifier (meaning that transactions in recent blocks appear first). If there are many transactions for a particular search, transactions may not contain all matching transactions. It is up to the caller to paginate these transactions using the max_block field.
+          items:
+            $ref: '#/components/schemas/BlockTransaction'
+        total_count:
+          description: total_count is the number of results for a given search. Callers typically use this value to concurrently fetch results by offset or to display a virtual page number associated with results.
+          type: integer
+          format: int64
+          minimum: 0
+          example: 5
+        next_offset:
+          description: next_offset is the next offset to use when paginating through transaction results. If this field is not populated, there are no more transactions to query.
+          type: integer
+          format: int64
+          minimum: 0
+          example: 5
     Error:
       description: Instead of utilizing HTTP status codes to describe node errors (which often do not have a good analog), rich errors are returned using this object. Both the code and message fields can be individually used to correctly identify an error. Implementations MUST use unique values for both fields.
       type: object