pdn: adjust naming to Google-style (excluding method names)

[openroad-ci]

Summary

adjust naming to Google-style (excluding method names)

Type of Change

• Refactoring

Impact

None

Verification

• I have verified that the local build succeeds (./etc/Build.sh).
• I have run the relevant tests and they pass.
• My code follows the repository's formatting guidelines.
• I have signed my commits (DCO).

[gemini-code-assist]

Code Review

This pull request performs an extensive refactoring of the PDN generation module to standardize naming conventions across the codebase. The changes primarily involve renaming enumeration members and static constants to use the kPascalCase prefix, as well as converting function parameters and local variables from camelCase to snake_case. The review feedback suggests further aligning with C++ style guidelines by using pointers instead of references for output parameters in the findRingShapes function.

[gemini-code-assist]

According to the Google C++ Style Guide, output parameters should be passed by pointer rather than by reference. This makes it explicit at the call site that the variable may be modified.

Suggested change

	std::vector<odb::dbSBox*> SRoute::findRingShapes(odb::dbNet* net,
	uint32_t& h_dy)
	std::vector<odb::dbSBox*> SRoute::findRingShapes(odb::dbNet* net,
	uint32_t* h_dy)

References

1. Function parameters should be passed by value or by const reference. Use pointers for output parameters. ^(link)

[gemini-code-assist]

As noted in the implementation, output parameters should be passed by pointer to adhere to the Google C++ Style Guide.

Suggested change

	std::vector<odb::dbSBox*> findRingShapes(odb::dbNet* net, uint32_t& h_dy);
	std::vector<odb::dbSBox*> findRingShapes(odb::dbNet* net, uint32_t* h_dy);

References

1. Function parameters should be passed by value or by const reference. Use pointers for output parameters. ^(link)

[github-actions]

clang-tidy review says "All clean, LGTM! 👍"