Added python script to automatically propagate the MOLE software license in root directory to all MATLAB/Octave scripts and C++ files

[deepanshu-zade]

What type of PR is this? (check all applicable)

• Refactor
• [ x ] Feature
• Bug Fix
• Optimization
• Example
• [ x ] Documentation

Description

Related Issues & Documents

• [ x ] I have created an Issue that is paired with this PR
• Closes Automatic propagation of MOLE software license to MATLAB/Octave scripts and C++ #320

QA Instructions, Screenshots, Recordings

Please replace this line with instructions on how to test your changes, a note
on the devices and browsers this has been tested on, as well as any relevant
images for UI changes.

Added/updated tests?

_We encourage you to test all code included with MOLE, including examples.

• [ x ] Yes
• No, and this is why: please replace this line with details on why tests
  have not been included
• I need help with writing tests

Read Contributing Guide and Code of Conduct

• [ x ] 📖 I have read the MOLE Contributing Guide: https://github.com/csrc-sdsu/mole/blob/main/CONTRIBUTING.md
• [ x ] 📖 I have read the MOLE Code of Conduct: https://github.com/csrc-sdsu/mole/blob/main/CODE_OF_CONDUCT.md

[optional] Are there any post deployment tasks we need to perform?

[optional] What gif best describes this PR or how it makes you feel?

[Tony-Drummond]

I review these changes with @deepanshu-zade and verified that it is working properly. This was a good suggestion by @pritkc and the implementation changes MATLAB/Octave script and C++ files.
We would like to first merge the branch PR #341 to main, and then this branch.

[pritkc]

Thank you @deepanshu-zade for the feature.

I exercised doc/utils/common/update_license.py locally: py_compile; correct insert/update/skip behavior for .m, .cpp, .h, and .hpp; recursive discovery; idempotent second pass; empty tree message; invalid CLI args; missing license path and missing target directory. All of that behaved as intended.

Approving based on these checks.