Support scientific notation representation in PPL

[LantaoJin]

Description

Numbers of scientific notation can be recognized in SQL, but not in PPL. With this PR, numbers of scientific notation can be identified as double in PPL as same as in SQL.
Here are valid examples of scientific notation representations: 9e1, +9e+1, 900e-1, 9.0e1, 9.0e+1, 9.0E1, .9e+2, 0.09e+3, 900.0e-1, -900.0E-1.

• Example query:

POST /_plugins/_ppl
{
  "query": """
  search source=t | eval `9e1`=9e1 | fields `9e1`
  """
}

• Result without this PR:

SyntaxCheckException: Failed to parse query due to offending symbol [e1] at: ... | eval 9e1=9e1' <--- HERE`

• Result with this PR:

{
  "schema": [
    {
      "name": "9e1",
      "type": "double"
    }
  ],
  "datarows": [
    [
      90
    ]
  ]
}

Verified the feature works both in v2 and v3.

Issues Resolved

Resolves #2826

Check List

• New functionality includes testing.
  • All tests pass, including unit test, integration test and doctest
• New functionality has been documented.
  • New functionality has javadoc added
  • New functionality has user manual doc added
• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[dai-chen]

Thanks for the changes!

[LantaoJin]

Gently ping @penghuo @vamsi-amazon @YANG-DB

[opensearch-trigger-bot]

This PR is stalled because it has been open for 30 days with no activity.

[opensearch-trigger-bot]

This PR is stalled because it has been open for 30 days with no activity.

[RyanL1997]

Hi @LantaoJin, just wanna check if this is still on track or we can close it?

[Swiddis]

@LantaoJin is this still being worked on? I see merge conflicts have been here for a while, overall lgtm if merge conflicts are resolved

[opensearch-trigger-bot]

This PR is stalled because it has been open for 2 weeks with no activity.