Prompt for the SubscriptionPlanApp

Please create a React-JS application for the SubscriptionPlanModule. The application  has to offer the following views for the user interface: 
    1. BreachDataExposureView 
    2. BreachDataTypeView 
    3. MilitaryUseCaseView 
    4. SubscriptionPlanView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 4 views are defined below.

1. The BreachDataExposureView must contain the following fields: 
    - name: BreachDataType   type: BreachDataType 
    - name: DataBreach   type: DataBreach 
    - name: EstimatedCount   type: LONG 
    - name: IsConfirmed   type: BOOL 
The data source for the [DataBreach] select control should be loaded from the relative URL: 
    "/SupportVendorService/databreach"   (HTTP-GET) 
The data source for the [BreachDataType] select control should be loaded from the relative URL: 
    "/SubscriptionPlanService/breachdatatype"   (HTTP-GET) 
An existing BreachDataExposure entity should be loaded from the relative URL: 
    "/SubscriptionPlanService/breachdataexposure/{id}"   (HTTP-GET) 
If a new BreachDataExposure entity has been created, the new entity should be posted to the relative URL: 
    "/SubscriptionPlanService/breachdataexposure"   (HTTP-POST) 
If an existing BreachDataExposure entity has been updated, the modified entity should be sent to the relative URL: 
    "/SubscriptionPlanService/breachdataexposure/{id}"   (HTTP-PUT) 
If an existing BreachDataExposure entity has to be deleted, the following relative URL should be called: 
    "/SubscriptionPlanService/breachdataexposure/{id}"   (HTTP-DELETE)

2. The BreachDataTypeView must contain the following fields: 
    - name: Description   type: STRING 
    - name: Name   type: STRING 
An existing BreachDataType entity should be loaded from the relative URL: 
    "/SubscriptionPlanService/breachdatatype/{id}"   (HTTP-GET) 
If a new BreachDataType entity has been created, the new entity should be posted to the relative URL: 
    "/SubscriptionPlanService/breachdatatype"   (HTTP-POST) 
If an existing BreachDataType entity has been updated, the modified entity should be sent to the relative URL: 
    "/SubscriptionPlanService/breachdatatype/{id}"   (HTTP-PUT) 
If an existing BreachDataType entity has to be deleted, the following relative URL should be called: 
    "/SubscriptionPlanService/breachdatatype/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following BreachDataExposure columns: 
    - column: BreachDataType 
    - column: EstimatedCount 
    - column: IsConfirmed 
    - column: DataBreach 
The table should have the title "BreachDataExposures" und the data must be loaded from the server with the following relative URL: 
    "/SubscriptionPlanService/breachdataexposure/breachdatatype/{id}"

3. The MilitaryUseCaseView must contain the following fields: 
    - name: ConflictName   type: STRING 
    - name: Country   type: STRING 
    - name: Description   type: STRING 
    - name: StartYear   type: LONG 
    - name: UnitType   type: STRING 
    - name: UsesDiscord   type: BOOL 
An existing MilitaryUseCase entity should be loaded from the relative URL: 
    "/SubscriptionPlanService/militaryusecase/{id}"   (HTTP-GET) 
If a new MilitaryUseCase entity has been created, the new entity should be posted to the relative URL: 
    "/SubscriptionPlanService/militaryusecase"   (HTTP-POST) 
If an existing MilitaryUseCase entity has been updated, the modified entity should be sent to the relative URL: 
    "/SubscriptionPlanService/militaryusecase/{id}"   (HTTP-PUT) 
If an existing MilitaryUseCase entity has to be deleted, the following relative URL should be called: 
    "/SubscriptionPlanService/militaryusecase/{id}"   (HTTP-DELETE)

4. The SubscriptionPlanView must contain the following fields: 
    - name: Features   type: STRING 
    - name: IsActive   type: BOOL 
    - name: MonthlyPriceUsd   type: DOUBLE 
    - name: Name   type: STRING 
An existing SubscriptionPlan entity should be loaded from the relative URL: 
    "/SubscriptionPlanService/subscriptionplan/{id}"   (HTTP-GET) 
If a new SubscriptionPlan entity has been created, the new entity should be posted to the relative URL: 
    "/SubscriptionPlanService/subscriptionplan"   (HTTP-POST) 
If an existing SubscriptionPlan entity has been updated, the modified entity should be sent to the relative URL: 
    "/SubscriptionPlanService/subscriptionplan/{id}"   (HTTP-PUT) 
If an existing SubscriptionPlan entity has to be deleted, the following relative URL should be called: 
    "/SubscriptionPlanService/subscriptionplan/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following NitroSubscription columns: 
    - column: EndedAt 
    - column: User 
    - column: AutoRenews 
    - column: SubscriptionPlan 
    - column: StartedAt 
The table should have the title "NitroSubscriptions" und the data must be loaded from the server with the following relative URL: 
    "/UserAccountService/nitrosubscription/subscriptionplan/{id}"