new chatqna readme template

[srinarayan-srikanthan]

Description

New chatqna master readme and xeon readme.

Issues

List the issue or RFC link this PR is working on. If there is no such link, please mark it as n/a.

Type of change

List the type of change like below. Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds new functionality)
• Breaking change (fix or feature that would break existing design and interface)
• Others (enhancement, documentation, validation, etc.)

Dependencies

NA

Tests

Describe the tests that you ran to verify your changes.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues found.

Scanned Files

None

[ftian1]

I am ok with the content, just think shall we have a script to do all instructions in the readme rather than running them one by one manually in the shell?

[chensuyue]

Please fix the preci issue, https://results.pre-commit.ci/run/github/775149161/1743735950.uNMP0jlnTmC6WssCEYdqXQ

[joshuayao]

Hi @srinarayan-srikanthan could you please resolve the comments? Thanks.

[joshuayao]

@XinyaoWa please help review the FaqGen related content, thanks.

[xiguiw]

Hi Sri,

FagGen is merged into ChatQnA.
We may need to update the new chatqna readme template document to cover FaqGen and ChatQnA.

FYI, here is the issue to be resolved.
#1726

[yinghu5]

LGTM, thank you!

[poussa]

Both README.md files have serious formatting issues (check the "View file" option).

Do we need the README_micellaneous.md file? It has duplicate content, text we want to get rid of, images look not very nice, etc.

[srinarayan-srikanthan]

what is the redundancy you are talking about @poussa ?

[lvliang-intel]

@srinarayan-srikanthan,

please fix pre-commit issue and comments.

[xiguiw]

@srinarayan-srikanthan

Shall FagGen be mentioned in this document? FagGen has been merged in ChatQnA

[yinghu5]

@srinarayan-srikanthan,

please fix pre-commit issue and comments.

thank you for review. we had fixed it in one commit, but it seems come back again. fix it again just now.