BIE's GUID should use a Top-Level ASBIEP's GUID

[hakjuoh]

The current database structure of the Top-Level BIE takes the following form.

---
title: Top-Level BIE
---
erDiagram
   TOP_LEVEL_ASBIEP ||--|| ASBIEP: uses
   ASBIEP ||--|| ABIE: related
   ASBIEP ||--|| ASCCP_MANIFEST: based_on
   ASCCP_MANIFEST }|--|| ASCCP: linked
   ASCCP_MANIFEST ||--|| ACC_MANIFEST: related
   ACC_MANIFEST }|--|| ACC: linked
   ABIE ||--|| ACC_MANIFEST: based_on
   TOP_LEVEL_ASBIEP ||--|| RELEASE: in
   ASCCP_MANIFEST ||--|| RELEASE: in
   ACC_MANIFEST ||--|| RELEASE: in
   TOP_LEVEL_ASBIEP {
        top_level_asbiep_id bigint PK
        asbiep_id bigint FK
        release_id bigint FK
   }
   ASBIEP {
      asbiep_id bigint PK, FK
      guid string
      role_of_abie_id bigint FK
      based_asccp_manifest_id bigint FK
   }
   ABIE {
      abie_id bigint PK, FK
      guid string
      based_acc_manifest_id bigint FK
   }
   ASCCP_MANIFEST {
      asccp_manifest_id bigint PK,FK
      release_id bigint FK
      den string
      asccp_id bigint FK
      role_of_acc_manifest_id bigint FK
   }
   ASCCP {
      asccp_id bigint PK, FK
      guid string
   }
   ACC_MANIFEST {
      acc_manifest_id bigint PK, FK
      release_id bigint FK
      den string
      acc_id bigint FK
   }
   ACC {
      acc_id bigint PK, FK
      guid string
   }
   RELEASE {
      release_id bigint PK, FK
      release_num string
   }

There are four GUIDs in the diagram: ASBIEP.GUID, ABIE.GUID, ASCCP.GUID, and ACC.GUID. In the past, we used the table 'TOP_LEVEL_ABIE,' and it was referencing the ABIE. In connectCenter 3, we changed 'TOP_LEVEL_ABIE' to 'TOP_LEVEL_ASBIEP,' but found out that the GUID on UIs still displays ABIE.GUID. Moreover, as we've seen in the issue #1592, some pages display ASCCP.GUID for the BIE's GUID.