Refactor Satellite APIs

1. APIs which have OutcomeReceiver as result accepter will report SATELLITE_RESULT_ILLEGALSTATE as a value of SatelliteExcetion through OutcomeReceiver instead of throwing IlldgalStateException.
   APIs which is non blocking API and has the result receiver as a form of Consumer<Integer> will have same procedure - report SATELLTIE_RESULT_ILLEGALSTATE instead of throwing IllgalStatException
2. APIs which throw runtime exception will throw rethrowAsRuntimeException instead of rethrowFromSystemServer for runtime exception as there has never been dead object exception in practical.
3. Removed SatelliteException from registerForNtnSignalStreangthChanged API, since there are no async error that can be reported after registration.

Bug: 306111250
Test: atest SatelliteManagerTest, SatelliteManagerTestOnMockService
Test: manual test with test application to invoke APIs on pixel
Change-Id: I301482e33f8684926fb670923026cbeaf105c560