HDDS-14708. Move server code out of ozone-common

[adoroszlai]

What changes were proposed in this pull request?

• Classes in org.apache.hadoop.ozone.om.lock are not for clients, so should be moved to ozone-interface-storage (where OMMetadataManager uses some of them).
• Classes org.apache.hadoop.ozone.om.S3Secret* are used only in ozone-manager, move to that module.
• Adjust dependencies accordingly.

https://issues.apache.org/jira/browse/HDDS-14708

How was this patch tested?

https://github.com/adoroszlai/ozone/actions/runs/22364980180

[adoroszlai]

@sadanand48 please take a look

[sodonnel]

There is no logic change here, so I am fine with it. I just worry about these reorganizations from a backport perspective, as it can make them more difficult. That said, we cannot prevent any code improvements just to make backports easier.

+1 from me for the change with the above in mind.

[ivandika3]

Thanks for the patch. Overall looks good.

I recall that the interface-storage module is used to separate storage and RPC proto (HDDS-4216).

In this case, should we instead move them to the ozone-manager module instead?

[adoroszlai]

In this case, should we simply move them to the ozone-manager module instead?

OMMetadataManager, defined in interface-storage, uses some of the lock interfaces, which in turn use other types from the ....om.lock package. Moved the rest to ozone-manager.