fix:(README):[eclipse-tractusx#1070] change png to svg part 2

docs/concept/#436-intermediate-status-handling/#436-intermediate-status-handling.md

@@ -35,7 +35,7 @@ The frontend must be able to display more nuanced status information, while the
 # Concept
 State machine:
 
-![Intermediate-status-handling.png](Intermediate-status-handling.png)
+![Intermediate-status-handling](Intermediate-status-handling.svg)
 
 | Step   | Description                                                                                                                                                                                                                                                                                                                                                                                                            | Resulting status shown to the user | Resulting internal status | Transition                                                                                                  |
 |--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|---------------------------|-------------------------------------------------------------------------------------------------------------|

docs/concept/#437-adapt-to-changes-of-industry-core/#437-adapt-to-changes-industry-core.md

@@ -146,7 +146,7 @@ values.yaml
 https://github.com/catenax-ng/tx-traceability-foss/blob/5b07a12830d6ecf9f3d0141d49bb89825cc86cc3/docs/src/uml-diagrams/arc42/cross-cutting/domain-model/domain-model.puml
 
 ### Changes in Detail View
-![DetailViewWithPartSiteInformation](DetailViewWithPartSiteInformation.png)
+![DetailViewWithPartSiteInformation](DetailViewWithPartSiteInformation.svg)
 
 
 # Definition of the Industry Core

docs/concept/#638-contractagreement-admin-view/#638-contractagreement-admin-view.md

@@ -119,11 +119,11 @@ User Journey Story:
 8. All reviewed contracts appear to comply with the guidelines. He notes down his result and logs himself out of the contract management section.
 
 ## BPMN
-![contractagreement-admin-view-bpmn.png](contractagreement-admin-view-bpmn.png)
+![contractagreement-admin-view-bpmn](contractagreement-admin-view-bpmn.svg)
 
 ## Frontend concept
 https://miro.com/app/board/uXjVOGBahIA=/?moveToWidget=3458764573051687012&cot=14
-![contractagreement-admin-view-frontend.png](contractagreement-admin-view-frontend.png)
+![contractagreement-admin-view-frontend](contractagreement-admin-view-frontend.svg)
 
 Contract data is called from the backend on a page-by-page basis.
 
@@ -138,7 +138,7 @@ POST api/contracts/request
 GET api/contracts/{tx-assetId}
 
 ### POST api/contracts/request sequence flow
-![get-all-contracts-sequenceflow.png](get-all-contracts-sequenceflow.png)
+![get-all-contracts-sequenceflow](get-all-contracts-sequenceflow.svg)
 
 #### 1. Frontend calls backend API to get contracts (paginated, sortable, filterable)
 
@@ -286,7 +286,7 @@ ___
 
 ### GET api/contracts/{tx-assetId} sequence flow
 
-![get-contract-sequenceflow.png](get-contract-sequenceflow.png)
+![get-contract-sequenceflow](get-contract-sequenceflow.svg)
 
 #### 1. Frontend calls backend API to get contract
 Input: tx-assetId

docs/concept/#737-contract-parts-link/#737-contract-parts-link.md

@@ -43,14 +43,14 @@ See also: https://miro.com/app/board/uXjVO5JVoho=
 In the contracts table a new single-item action is added to the action menu.
 The action is called "View parts" with the parts icon.
 The tooltip when hovering over the action says "View parts using this contract".
-![contracts-table-new-action.png](contracts-table-new-action.png)
+![contracts-table-new-action](contracts-table-new-action.svg)
 
 The column "Contract ID" must be added to part tables AsBuilt and AsPlanned.
-![parts-tables-contract-column.png](parts-tables-contract-column.png)
+![parts-tables-contract-column](parts-tables-contract-column.svg)
 
 After clicking on the action, the user is taken to the parts table filtered for the selected contract.
 Clicking back in the browser, brings the user back to the contracts table.
-![parts-tables-contract-column-filtered.png](parts-tables-contract-column-filtered.png)
+![parts-tables-contract-column-filtered](parts-tables-contract-column-filtered.svg)
 
 # Additional Details
 Given the dynamic nature of ongoing development, there might be variations between the conceptualization and the current implementation. For the latest status, refer to the documentation.

docs/concept/#774-messages-to-multiple-bpns/#774-messages-to-multiple-bpns.md

@@ -358,7 +358,7 @@ BPNL0A will have those 3 messages and additionally the message sent to BPN2Y, wh
 In the notification detail view, the message history will be changed according to the frontend concept:
 
 **Creator/Sender:**
-![frontend-notification-detail-view-sender.png](frontend-notification-detail-view-sender.png)
+![frontend-notification-detail-view-sender](frontend-notification-detail-view-sender.svg)
 
 The overview must be adapted to the backend changes.
 
@@ -373,15 +373,15 @@ Additionally, the user is able to edit the notification, send it or close it. (D
 Clicking "send" will send messages to all BPNLs, where the last state was "CREATED" all messages that are in the state "CREATED". Other
 
 **Recipient:**
-![frontend-notification-detail-view-recipient.png](frontend-notification-detail-view-recipient.png)
+![frontend-notification-detail-view-recipient](frontend-notification-detail-view-recipient.svg)
 
 For the recipient not much changes, since a notification can only be received by a single BPNL. The overview and the message history should be aligned with the view from the sender.
 The actions remain the same.
 
 #### Create/Edit notifications
 When creating or editing notifications, the user must be able to add/remove multiple BPNLs.
 This should be made possible by having an autocomplete in the input text field. And showing selected BPNLs as removable chips:
-![frontend-create-notification.png](frontend-create-notification.png)
+![frontend-create-notification](frontend-create-notification.svg)
 (-> identical for Edit Notification)
 
 # References

docs/concept/#849-notifications-to-multiple-bpns/#849-notifications-to-multiple-bpns.md

@@ -85,11 +85,11 @@ There is no possibility to create a new notification from the "Edit notification
 If the user wants to send an existing notification to a different BPN, he must copy the data and use the "Create notification" process.
 
 ## Frontend
-![multiple-bpns-modals.png](multiple-bpns-modals.png)
-![notification-creation-bpn-selection.png](notification-creation-bpn-selection.png)
+![multiple-bpns-modals](multiple-bpns-modals.svg)
+![notification-creation-bpn-selection](notification-creation-bpn-selection.svg)
 
 New case label:
-![case-label.png](case-label.png)
+![case-label](case-label.svg)
 
 See https://miro.com/app/board/uXjVO5JVoho=/?moveToWidget=3458764586657591852&cot=10