Is the SEPARATOR_LENGTH_IN_MARKDOWN_FORMAT necessary? If yes, how to decide it?

> Please provide us with the following information:
> ---------------------------------------------------------------

### This issue is for a: (mark with an `x`)
```
- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)
```

### Minimal steps to reproduce
>

### Any log messages given by the failure
>

### Expected/desired behavior
>

### OS and Version?
> Windows

### Versions
> 11

### Mention any other details that might be useful
Thanks for providing a [notebook](https://github.com/Azure-Samples/document-intelligence-code-samples/blob/main/Python(v4.0)/Retrieval_Augmented_Generation_(RAG)_samples/sample_identify_and_merge_cross_page_tables.ipynb) for merging tables across pages
For vertical table, is the SEPARATOR_LENGTH_IN_MARKDOWN_FORMAT necessary? as when there is no paragraph in between, there are only page header/footer/number between two tables, the two tables can be merged if they have the same number of columns.
If it is necessary, how can it be decided? It is “2” in the notebook but due to the inclusion of markdown for page header/footer/number and page break when calculating the offset, there are more than 2 characters between two tables. So 2 is too small.
> ---------------------------------------------------------------
> Thanks! We'll be in touch soon.

開啟連結的 sample_identify_and_merge_cross_page_tables.ipynb，並找出 SEPARATOR_LENGTH_IN_MARKDOWN_FORMAT。追蹤頁面標題、頁尾、頁碼和分頁符號的 Markdown 如何造成垂直表格之間的偏移，然後將 notebook 中的值 2 與所描述的情況進行比較。當必要性和決策規則已記錄，或已根據範例中的證據回答 issue 時，即視為完成。

由索引模型根據 Issue 內容生成。