Add NOTICE as disclaimer

[coketaste]

📋 Description

Brief description of the changes in this pull request.

🔍 Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📚 Documentation update
• 🧪 Test improvements
• 🔧 Code refactoring
• 🎨 Style/formatting changes

🎯 Related Issues

Fixes #(issue number)
Relates to #(issue number)

📍 Module/Area Affected

• Module 1 - Fundamentals
• Module 2 - Mathematics
• Module 3 - Programming
• Module 4 - Algorithms
• Module 5 - Error Correction
• Module 6 - Machine Learning
• Module 7 - Hardware
• Module 8 - Applications
• Documentation
• Testing/CI
• Project infrastructure

🧪 Testing

Describe how you tested your changes:

✅ Completed Testing

• All affected examples run without errors
• Help text is accurate and informative
• Visualizations display correctly
• Parameter validation works as expected
• Code follows project style guidelines

🖥️ Testing Environment

• OS: (e.g., Ubuntu 20.04)
• Python Version: (e.g., 3.9.7)
• Qiskit Version: (e.g., 1.0.0)

📝 Test Commands

# Commands used to test the changes
python module_x/example.py --help
python module_x/example.py --parameter value

📸 Screenshots (if applicable)

Include screenshots for visual changes, new visualizations, or UI improvements.

📚 Documentation Changes

• Updated relevant README files
• Added/updated docstrings
• Updated module documentation
• Added code comments for complex sections

⚡ Performance Impact

• No performance impact
• Improves performance
• May impact performance (please describe)

🔄 Breaking Changes

If this introduces breaking changes, please describe:

• What will break?
• How can users migrate?
• Is this change necessary?

📋 Checklist

Code Quality

• My code follows the project's style guidelines
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have added docstrings to new functions and classes

Testing

• I have tested these changes locally
• Existing examples still work correctly
• New functionality has been tested
• Error handling has been tested

Documentation

• I have made corresponding changes to the documentation
• I have updated relevant README files
• I have added appropriate comments to the code

Educational Value

• Changes maintain or improve educational value
• Learning objectives are clear
• Examples are appropriate for the target skill level
• Concepts are explained clearly

🎓 Educational Impact

How do these changes improve the learning experience?

• What new concepts do they teach?
• How do they fit into the overall curriculum?
• What skill level are they appropriate for?

🤝 Review Notes

Anything specific you'd like reviewers to focus on?

📈 Future Work

Any follow-up work that should be done in future PRs?

---

Thank you for contributing to Quantum Computing 101! 🚀⚛️

[Copilot]

Pull Request Overview

Adds a NOTICE file to the repository containing educational disclaimers, source attributions, and legal compliance information for the quantum computing educational project.

• Establishes clear educational purpose disclaimer
• Documents third-party open-source dependencies and their licenses
• Provides compliance information regarding export control, patents, and academic integrity

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

There's an extra space at the end of line 20 after 'Google Quantum AI'. This trailing whitespace should be removed for consistency.

Suggested change

	- Cirq (Apache License 2.0) - Google Quantum AI
	- Cirq (Apache License 2.0) - Google Quantum AI