WpRequestBuilder

[oguzkocer]

Builds on #114 and introduces WpRequestBuilder as a replacement for WpApiHelper. The usage becomes:

// Before (from Kotlin)
apiHelper.retrieveUserRequest(userId, context)
// After (from Kotlin)
requestBuilder.users().retrieve(userId, context)

I was initially going to use the WpApi name as a general encapsulation, but while updating the Swift implementation, I realized it'd create a clash. Also, I think WpRequestBuilder is a more suitable name if we want to just keep it for request building. I still don't like the Wp prefix, but for now, this is consistent with rest of the naming.

Note that it's using Wp instead of WP as the prefix, because the bindings are generated with this prefix and the Rust layer will be updated to use it, so it's consistent everywhere. I didn't want to use WP just to change it in a later PR.

I've also updated the Current suffix for users with Me. This is consistent with the API endpoint and should make it easier to look up documentation if it's needed. I should have gone with this from the start and only didn't do so because I felt weird using Me.

To Test

• make test-server && make dump-mysql && make backup-wp-content-plugins
• cargo test --test '*' -- --nocapture --test-threads 1
• cd native/kotlin && ./gradlew :api:kotlin:integrationTest cAT

[jkmassel]

No memory leaks related to this code, and the changes look straightforward.