Generalise profiling workflow to support multiple model configs

[minghangli-uni]

The current profiling workflow was originally implemented with esm1.6 specific use cases, including:

• hardcoded layout structures
• esm1.6 specific layout tuple handling
• model specific perturbation block construction
• assumptions about layout and search configs

While this worked well for the original scope, it makes it more difficult to introduce new models without modifying core workflow logic. Since I am incorporating OM3 profiling as part of this PR #48, I'll propose and outline some changes to that same PR to generalise the workflow a bit so it can be model agnostic and extensible.

[manodeep]

Yes, this is definitely an issue and needs to be generalised

[micaeljtoliveira]

Having something fully generic is part of our plans, but I think it's always better to start from a couple of specific cases and then generalize them, instead of designing something fully generic from the beginning. So, from that point of view, having a workflow for OM3, even if it's doesn't fully reuse what's there from ESM1.6 is fine and a step in the right direction.