[Feature]: AutoDeploy: load_hook hierarchy

🚀 The feature, motivation and pitch

Right now, we register all load hooks in the parent module (the parent GM). This can cause issues in the order of load hooks. Broadly speaking load hook order is as follows:

1. Load hooks in parent modules before load hooks in children modules
2. Order of registration of load hooks

Right now, registering everything in the parent GM can cause issues if for example a custom modeling code has load hooks in the child class, e.g., see this issue: https://nvidia.slack.com/archives/C08T55LHSG4/p1767113040245849?thread_ts=1766676954.143199&cid=C08T55LHSG4

Alternatives

No response

Additional context

No response

Before submitting a new issue...

• Make sure you already searched for relevant issues, and checked the documentation and examples for answers to frequently asked questions.