ES mapper_parsing_exception error with testnet-6.1.0

[abitmore]

Bug Description
The test-6.1.0 tag is unable to sync if the elasticsearch plugin is enabled and the elasticsearch-operation-object startup option is true. Error messages:

"error":{"type":"mapper_parsing_exception","reason":"failed to parse field [operation_history.op_object.restrictions.argument] of type [text] in document with id '2.9.84598426'. Preview of field's value: '{restriction_type=0, argument=[8, 1.3.0], extensions=[], member_index=1}'","caused_by":{"type":"illegal_state_exception","reason":"Can't get text on a START_OBJECT at 1:1248"}}

It's related to the custom active authority feature.

Impacts
Describe which portion(s) of BitShares Core may be impacted by this bug. Please tick at least one box.

• API (the application programming interface)
• Build (the build process or something prior to compiled code)
• CLI (the command line wallet)
• Deployment (the deployment process after building such as Docker, Travis, etc.)
• DEX (the Decentralized EXchange, market engine, etc.)
• P2P (the peer-to-peer network for transaction/block propagation)
• Performance (system or user efficiency, etc.)
• Protocol (the blockchain logic, consensus, validation, etc.)
• Security (the security of system or user data, etc.)
• UX (the User Experience)
• Other (please add below) : ElasticSearch History plugin

Steps To Reproduce
Steps to reproduce the behavior (example outlined below):

1. Execute API call '...'
2. Using JSON payload '...'
3. Received response '...'
4. See error in screenshot

Expected Behavior
A clear and concise description of what you expected to happen.

Screenshots (optional)
If applicable, add screenshots to help explain process flow and behavior.

Host Environment
Please provide details about the host environment. Much of this information can be found running: witness_node --version.

• Host OS: Ubuntu 20.04 LTS
• Host Physical RAM /
• BitShares Version: test-6.1.0
• OpenSSL Version: 1.1.1s
• Boost Version: 1.71

Additional Context (optional)
Add any other context about the problem here.

CORE TEAM TASK LIST

• Evaluate / Prioritize Bug Report
• Refine User Stories / Requirements
• Define Test Cases
• Design / Develop Solution
• Perform QA/Testing
• Update Documentation

[abitmore]

Fixed by #2681.