Prompt for the RegulatoryRegionApp

Please create a React-JS application for the RegulatoryRegionModule. The application  has to offer the following views for the user interface: 
    1. BusinessProfileView 
    2. RegulatoryRegionView 
    3. SecuritySettingView 
    4. UserRegionView 
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 BusinessProfileView must contain the following fields: 
    - name: BusinessName   type: STRING 
    - name: Category   type: STRING 
    - name: CreatedAt   type: DATE 
    - name: IsVerified   type: BOOL 
    - name: SupportEmail   type: STRING 
    - name: SupportPhone   type: STRING 
    - name: UserAccount   type: UserAccount 
    - name: UsesCloudApi   type: BOOL 
    - name: WebsiteUrl   type: STRING 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing BusinessProfile entity should be loaded from the relative URL: 
    "/RegulatoryRegionService/businessprofile/{id}"   (HTTP-GET) 
If a new BusinessProfile entity has been created, the new entity should be posted to the relative URL: 
    "/RegulatoryRegionService/businessprofile"   (HTTP-POST) 
If an existing BusinessProfile entity has been updated, the modified entity should be sent to the relative URL: 
    "/RegulatoryRegionService/businessprofile/{id}"   (HTTP-PUT) 
If an existing BusinessProfile entity has to be deleted, the following relative URL should be called: 
    "/RegulatoryRegionService/businessprofile/{id}"   (HTTP-DELETE)

2. The RegulatoryRegionView must contain the following fields: 
    - name: DataRetentionPolicy   type: STRING 
    - name: Description   type: STRING 
    - name: GdprApplies   type: BOOL 
    - name: Name   type: STRING 
An existing RegulatoryRegion entity should be loaded from the relative URL: 
    "/RegulatoryRegionService/regulatoryregion/{id}"   (HTTP-GET) 
If a new RegulatoryRegion entity has been created, the new entity should be posted to the relative URL: 
    "/RegulatoryRegionService/regulatoryregion"   (HTTP-POST) 
If an existing RegulatoryRegion entity has been updated, the modified entity should be sent to the relative URL: 
    "/RegulatoryRegionService/regulatoryregion/{id}"   (HTTP-PUT) 
If an existing RegulatoryRegion entity has to be deleted, the following relative URL should be called: 
    "/RegulatoryRegionService/regulatoryregion/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following UserRegion columns: 
    - column: EffectiveFrom 
    - column: EffectiveTo 
    - column: RegulatoryRegion 
    - column: UserAccount 
The table should have the title "UserRegions" und the data must be loaded from the server with the following relative URL: 
    "/RegulatoryRegionService/userregion/regulatoryregion/{id}"

3. The SecuritySettingView must contain the following fields: 
    - name: FingerprintLockEnabled   type: BOOL 
    - name: IsTwoStepVerificationEnabled   type: BOOL 
    - name: LastUpdatedAt   type: DATE 
    - name: PasskeyEnabled   type: BOOL 
    - name: SecretCodeEnabled   type: BOOL 
    - name: TwoStepEmail   type: STRING 
    - name: UserAccount   type: UserAccount 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing SecuritySetting entity should be loaded from the relative URL: 
    "/RegulatoryRegionService/securitysetting/{id}"   (HTTP-GET) 
If a new SecuritySetting entity has been created, the new entity should be posted to the relative URL: 
    "/RegulatoryRegionService/securitysetting"   (HTTP-POST) 
If an existing SecuritySetting entity has been updated, the modified entity should be sent to the relative URL: 
    "/RegulatoryRegionService/securitysetting/{id}"   (HTTP-PUT) 
If an existing SecuritySetting entity has to be deleted, the following relative URL should be called: 
    "/RegulatoryRegionService/securitysetting/{id}"   (HTTP-DELETE)

4. The UserRegionView must contain the following fields: 
    - name: EffectiveFrom   type: DATE 
    - name: EffectiveTo   type: DATE 
    - name: RegulatoryRegion   type: RegulatoryRegion 
    - name: UserAccount   type: UserAccount 
The data source for the [RegulatoryRegion] select control should be loaded from the relative URL: 
    "/RegulatoryRegionService/regulatoryregion"   (HTTP-GET) 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing UserRegion entity should be loaded from the relative URL: 
    "/RegulatoryRegionService/userregion/{id}"   (HTTP-GET) 
If a new UserRegion entity has been created, the new entity should be posted to the relative URL: 
    "/RegulatoryRegionService/userregion"   (HTTP-POST) 
If an existing UserRegion entity has been updated, the modified entity should be sent to the relative URL: 
    "/RegulatoryRegionService/userregion/{id}"   (HTTP-PUT) 
If an existing UserRegion entity has to be deleted, the following relative URL should be called: 
    "/RegulatoryRegionService/userregion/{id}"   (HTTP-DELETE)