Adding PPL GET Api endpoint

[YANG-DB]

Description

Adding support for PPL GET endpoint (to match existing POST endpoint)

Issues Resolved

#2463

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.41%. Comparing base (efb159a) to head (889b5b2).
Report is 197 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##               main    #2464   +/-   ##
=========================================
  Coverage     95.41%   95.41%           
  Complexity     5000     5000           
=========================================
  Files           479      479           
  Lines         13950    13950           
  Branches        937      937           
=========================================
  Hits          13310    13310           
  Misses          618      618           
  Partials         22       22           

Flag	Coverage Δ
sql-engine	95.41% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Swiddis]

I'm trying to understand why there are a lot of these mini classes that just change the method. My understanding is it's trying to subtly change the extended test with a new method, but I'm not sure I follow why this is better than adding more tests to the base test class that use different methods.

[YANG-DB]

It's just the easiest way in java to separate different aspects of the test into different classes - each class is responsible for one thing - the "single responsibility" principle

[penghuo]

Do we need to add GET api test in each IT? E.g. DedupCommandIT is focus on IntegrationTest instead of dedup command test, instead of REST interface.
Add GET API in doc test (endpoint.rst) should be enough?

[Swiddis]

Should we default to post and not raise an exception that non-post/get isn't supported?

[YANG-DB]

The default is the POST ...
There is a default error in netty server that returns the appropriate text if no endpoint is defined for the specific url or http method

[Swiddis]

Closing as stale -- reopen if needed