fix: getRecords action page→take/skip + prisma engine fix + CLI fixes

- getRecords automation action: translate page/pageSize to skip/take
  before calling the records API (which ignores page/pageSize, causing
  pagination to always return first 100 records)
- Add postbuild script to restore correct prisma engine binary after
  nest build (which generates an incompatible engine causing SIGSEGV)
- CLI fixes (from earlier commits):
  - deleteRecords: query params instead of JSON body
  - deleteTable: add /base/{baseId} prefix

dist/lib/client.js

@@ -59,8 +59,9 @@ class Client {
     updateTable(tableId, body) {
         return this.call('PUT', `/api/table/${tableId}`, body);
     }
-    deleteTable(tableId) {
-        return this.call('DELETE', `/api/table/${tableId}`);
+    deleteTable(tableId, baseId) {
+        const base = baseId ?? this.cfg.baseId;
+        return this.call('DELETE', `/api/base/${base}/table/${tableId}`);
     }
     // ---- field ----
     listFields(tableId) {
@@ -116,8 +117,9 @@ class Client {
     updateRecordOne(recordId, body) {
         return this.call('PATCH', `/api/record/${recordId}`, body);
     }
-    deleteRecord(tableId, body) {
-        return this.call('DELETE', `/api/table/${tableId}/record`, body);
+    deleteRecords(tableId, recordIds) {
+        const qs = recordIds.map((id) => `recordIds=${encodeURIComponent(id)}`).join('&');
+        return this.call('DELETE', `/api/table/${tableId}/record?${qs}`);
     }
     // ---- view ----
     listViews(tableId) {