Issue:
Bug: refactor(dynamic_routing): add non_deterministic value in SuccessBasedRoutingConclusiveState type



## Description
<!-- Describe your changes in detail -->
This will add a value `non_deterministic` in `SuccessBasedRoutingConclusiveState` type.

Pull request description:
## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD

## Description
<!-- Describe your changes in detail -->
This will add a value `non_deterministic` in `SuccessBasedRoutingConclusiveState` type.

### Additional Changes

- [ ] This PR modifies the API contract
- [x] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment variables

<!--
Provide links to the files with corresponding changes.

Following are the paths where you can find config files:
1. `config`
2. `crates/router/src/configs`
3. `loadtest/config`
-->


## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the issue here.

If you don't have an issue, we'd recommend starting with one first so the PR
can focus on the implementation (unless it is an obvious bug or documentation fix
that will have little conversation).
-->


## How did you test it?
<!--
Did you write an integration/unit/API test to verify the code changes?
Or did you test this change manually (provide relevant screenshots)?
-->
1. Toggle Success Based routing for the merchant.
```
curl --location --request POST 'http://localhost:8080/account/xxxxxx/business_profile/xxxxxxx/dynamic_routing/success_based/toggle?enable=metrics' \
--header 'api-key: xxxxxxx'
```

2. Create a payment that goes in processing state or any non terminal state.
3. Check the `dynamic_routing_stats` table for the `payment_id` for the `non_determinisctic`.


## Checklist
<!-- Put an `x` in the boxes that apply -->

- [x] I formatted the code `cargo +nightly fmt --all`
- [x] I addressed lints thrown by `cargo clippy`
- [x] I reviewed the submitted code
- [ ] I added unit tests for my changes where possible


Testing:

1. Toggle Success Based routing for the merchant.
```
curl --location --request POST 'http://localhost:8080/account/xxxxxx/business_profile/xxxxxxx/dynamic_routing/success_based/toggle?enable=metrics' \
--header 'api-key: xxxxxxx'
```

2. Create a payment that goes in processing state or any non terminal state.
3. Check the `dynamic_routing_stats` table for the `payment_id` for the `non_determinisctic`.

Patch:
diff --git a/migrations/2024-12-18-124527_add_new_value_in_success_based_routing_conclusive_state/down.sql b/migrations/2024-12-18-124527_add_new_value_in_success_based_routing_conclusive_state/down.sql
new file mode 100644
index 00000000000..2a3866c86d4
--- /dev/null
+++ b/migrations/2024-12-18-124527_add_new_value_in_success_based_routing_conclusive_state/down.sql
@@ -0,0 +1,2 @@
+-- This file should undo anything in `up.sql`
+SELECT 1;
diff --git a/migrations/2024-12-18-124527_add_new_value_in_success_based_routing_conclusive_state/up.sql b/migrations/2024-12-18-124527_add_new_value_in_success_based_routing_conclusive_state/up.sql
new file mode 100644
index 00000000000..9e4a259c7ae
--- /dev/null
+++ b/migrations/2024-12-18-124527_add_new_value_in_success_based_routing_conclusive_state/up.sql
@@ -0,0 +1,12 @@
+-- Your SQL goes here
+DO $$
+BEGIN
+    IF NOT EXISTS (
+        SELECT 1
+        FROM pg_enum 
+        WHERE enumlabel = 'non_deterministic'
+          AND enumtypid = (SELECT oid FROM pg_type WHERE typname = 'SuccessBasedRoutingConclusiveState')
+    ) THEN
+        ALTER TYPE "SuccessBasedRoutingConclusiveState" ADD VALUE 'non_deterministic';
+    END IF;
+END $$;