adding documentation for model group id

[dhrubo-os]

Description

[From 2.8 we need to provide model group id during registering the model. So we needed to reflect that change. Also from 2.7 we are supporting to register pre-trained models. So I added detailed explanation in the notebook for better customer experience. ]

Issues Resolved

[List any issues this PR will resolve]

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[codecov]

Codecov Report

Merging #176 (e7bb142) into main (634726f) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #176      +/-   ##
==========================================
+ Coverage   90.79%   90.80%   +0.01%     
==========================================
  Files          37       37              
  Lines        4042     4047       +5     
==========================================
+ Hits         3670     3675       +5     
  Misses        372      372              

Impacted Files	Coverage Δ
opensearch_py_ml/ml_commons/__init__.py	100.00% <100.00%> (ø)
opensearch_py_ml/ml_commons/ml_common_utils.py	100.00% <100.00%> (ø)
opensearch_py_ml/ml_commons/ml_commons_client.py	80.15% <100.00%> (+0.15%)	⬆️
opensearch_py_ml/ml_commons/model_uploader.py	97.43% <100.00%> (-0.27%)	⬇️

[rbhavna]

There will be some changes to create model group automatically in the backend when first model version is registered. We might need to reflect those changes to the documentation including this PR.

[opensearch-trigger-bot]

The backport to 1.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.x 1.x
# Navigate to the new working tree
cd .worktrees/backport-1.x
# Create a new branch
git switch --create backport/backport-176-to-1.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 03199fbc7a3a055b9a85971634ee5c94e1354c32
# Push it to GitHub
git push --set-upstream origin backport/backport-176-to-1.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.x

Then, create a pull request where the base branch is 1.x and the compare/head branch is backport/backport-176-to-1.x.