Bug: Update broken readme icon



Updating broken readme icon along with reposition of the hero image
diff --git a/README.md b/README.md
index ccdd6e19b6d..10fdb6afc76 100644
--- a/README.md
+++ b/README.md
@@ -22,7 +22,7 @@ The single API to access payment ecosystems across 130+ countries</div>
 
 <p align="center">
   <a href="https://github.com/juspay/hyperswitch/actions?query=workflow%3ACI+branch%3Amain">
-    <img src="https://github.com/juspay/hyperswitch/workflows/CI/badge.svg" />
+    <img src="https://github.com/juspay/hyperswitch/workflows/CI-push/badge.svg" />
   </a>
   <a href="https://github.com/juspay/hyperswitch/blob/main/LICENSE">
     <img src="https://img.shields.io/github/license/juspay/hyperswitch" />
@@ -44,7 +44,6 @@ The single API to access payment ecosystems across 130+ countries</div>
 </p>
 
 <hr>
-<img src="./docs/imgs/switch.png" />
 
 Hyperswitch is a community-led, open payments switch designed to empower digital businesses by providing fast, reliable, and affordable access to the best payments infrastructure.
 
@@ -58,7 +57,8 @@ Here are the components of Hyperswitch that deliver the whole solution:
 
 Jump in and contribute to these repositories to help improve and expand Hyperswitch!
 
-<br>
+<img src="./docs/imgs/switch.png" />
+
 
 <a href="#Quick Setup">
   <h2 id="quick-setup">⚡️ Quick Setup</h2>

TOC icon and reposition of the hero image in readme

## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [x] Documentation
- [ ] CI/CD

## Description
<!-- Describe your changes in detail -->
Updated the icon of CI Push and repositioned the hero image
closes #6449 

### Additional Changes

- [ ] This PR modifies the API contract
- [ ] 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)?
-->


## Checklist
<!-- Put an `x` in the boxes that apply -->

- [ ] I formatted the code `cargo +nightly fmt --all`
- [ ] I addressed lints thrown by `cargo clippy`
- [x] I reviewed the submitted code
- [ ] I added unit tests for my changes where possible
