fix: the "table_index" is incorrect in LayoutParsingPipelineV2 #4678
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
When the LayoutParsingPipelineV2 class is processing, if there are nested or complex tables in the image, layout_det_res and table_res_list will return overlapping table information. Then, the remove_overlap_blocks method deletes the overlapping blocks from layout_det_res, resulting in an inconsistent order between layout_det_res and table_res_list, causing problems in the calculation of table_index in the get_layout_parsing_objects method. Finally, the incorrect table content is assigned to the LayoutBlock. Currently, the fix method is to calculate the table_index in the get_layout_parsing_objects method by using the overlapping ratio of the table bounding boxes.