lastpass: use explicit JSON serialisation in response transform

A Beats regression (elastic/beats#50384) changed response body
template values from mapstr.M (whose String method produces JSON)
to plain map[string]interface{} (whose String method produces Go
map syntax). This breaks the detailed_shared_folder response
transform which renders the whole body with value_type: json.

Use the toJSON template function to serialise the body explicitly,
bypassing the implicit serialisation path.

Updates #18754
Updates #19767
Updates #19774

Author: efd6

packages/lastpass/changelog.yml

@@ -1,4 +1,9 @@
 # newer versions go on top
+- version: "1.23.1"
+  changes:
+    - description: Fix serialisation of detailed_shared_folder data stream response.
+      type: bugfix
+      link: https://github.com/elastic/integrations/pull/
 - version: "1.23.0"
   changes:
     - description: Use new `release` field for agentless deployment mode to establish as beta.

packages/lastpass/data_stream/detailed_shared_folder/agent/stream/httpjson.yml.hbs

@@ -37,7 +37,7 @@ request.transforms:
 response.transforms:
   - set:
       target: body.data
-      value: '[[.last_response.body]]'
+      value: '[[toJSON .last_response.body]]'
       value_type: json
 response.pagination:
   - set:

packages/lastpass/manifest.yml

@@ -1,7 +1,7 @@
 format_version: "3.3.2"
 name: lastpass
 title: LastPass
-version: "1.23.0"
+version: "1.23.1"
 description: Collect logs from LastPass with Elastic Agent.
 type: integration
 categories: