v2 scorer types clean up

[lebraat]

User Story:

As a developer using v2
I want to skip choosing a scorer type since they are no longer relevant
So that I can onboard more quickly and without confusion.

Acceptance Criteria

GIVEN ... A developer using the developer portal
WHEN ... they are creating a scorer
THEN ... they are not presented the 'choose a type of scorer' page

Product & Design Links:

We discussed this during our weekly meeting.

For new developers -- since they will be using v2 moving forward, they should not need to select a scorer type anymore since we are delivering both the unique humanity numerical score as well as the binary score/threshold via every score payload.

For existing developers -- they've already selected their scorer type, so we need to ensure both unique humanity (numerical) and binary scorers are delivering the same payloads for v2, while still delivering the same payloads via v1.

Tech Details:

In the developer portal, we need to remove the 'type of scorer' page from the scorer creation setup.

In the v2 payload, we need to ensure the Score object's score field returns the numerical score and not the binary for both existing binary and numerical scorers.

In the v1 payload, we need to ensure the score object still delivers the numerical score for numerical scorer types, and that binary scores deliver with binary scorer types.