fix: version document for latest version

[sanyamjain300]

PR Checklist

• Added label to the Pull Request for easier discoverability and search
• Commit Message meets guidelines as indicated in the URL https://github.com/intel-retail/automated-self-checkout/blob/main/CONTRIBUTING.md
• Every commit is a single defect fix and does not mix feature addition or changes
• Unit Tests have been added for new changes
• Updated Documentation as relevant to the changes
• All commented code has been removed
• If you've added a dependency, you've ensured license is compatible with repository license and clearly outlined the added dependency.
• PR change contains code related to security
• PR introduces changes that breaks compatibility with other modules (If YES, please provide details below)

What are you changing?

When directing to https://intel-retail.github.io/automated-self-checkout/latest will redirect user to the latest version release notes.

Issue this PR will close

close: #498

Anything the reviewer should know when reviewing this PR?

Test Instructions if applicable

Can test it by doing the github deploy and then using URL: https://intel-retail.github.io/automated-self-checkout/latest to test the working of code or else it can be tested locally by using the URL: '/latest'.

If the there are associated PRs in other repositories, please link them here (i.e. intel-retail/automated-self-checkout )

[NeethuES-intel]

@sanyamjain300 did you test this PR by github deploy and then using URL: https://intel-retail.github.io/automated-self-checkout/latest ? How did you test ?

[sanyamjain300]

Actually I have tested it in localhost, shall I test it in github deploy too?

[NeethuES-intel]

@sanyamjain300 did you test this PR by github deploy and then using URL: https://intel-retail.github.io/automated-self-checkout/latest ? How did you test ?

@sanyamjain300 we need this process automated with every github-deploy action. How does adding html page help ? Can you explain the concept ?
This is an issue with mkdocs deployment using mike tool for maintaining multiple versions of documentations. Whichever version gets deployed last is set as latest. More details in this PR - #504

[NeethuES-intel]

Actually I have tested it in localhost, shall I test it in github deploy too?

@sanyamjain300 we need this process automated.

[sanyamjain300]

Okay, I got it now. I will do the necessary updates.