[EXTERNAL] forum and real-time-forum: Allow both gofrs/uuid and google/uuid

[sadiqui]

This PR updates allowed packages in forum and real-time-forum projects to permit google/uuid for UUID generation along with gofrs/uuid. The projects are web-based forums with a generel-purpose use case, where UUIDs are primarily used for session tokens. Since the projects are written in Go (which was designed at Google), it's reasonable to allow both UUID implementations to give learners flexibility while ensuring compatibility with best practices in the Go ecosystem. This change does not introduce new dependencies but broadens the allowed options for UUID handling within the projects.

Information & Rationale:

• google/uuid is developed by Google, making it a natural fit for Go-based projects. It is efficient, lightweight, and optimized for performance, aligning with Go’s design philosophy.
• gofrs/uuid is designed as a secure replacement for satori/go.uuid, addressing past vulnerabilities. It prioritizes correctness and safe randomness handling.

Feature	gofrs/uuid	google/uuid
Security Focus	✅ Strong	⚠️ Less Emphasis
Performance	⚠️ Slightly Slower	✅ More Efficient
Active Maintenance	✅ Yes	✅ Yes
Compliance	✅ RFC 4122	✅ RFC 4122
Recommended Use Case	Security-sensitive apps	General-purpose UUIDs