proto: fix topic name fields to comply with API standards

[bojand]

This PR addresses a few instances where we use name as a topic name, and changes it to topic_name as per our API standards.

There are a handful of other cases where name literal is used, but it is within a Topic message or similar, so I left those as is... But I am open to changing them.

There are other instances of name being used for resource names, such as user, or role, transform, or connector.... I did not touch those... Should we change those? This is probably our opportunity.

[github-actions]

The latest Buf updates on your PR. Results from workflow Buf CI / push-module (pull_request).

Build	Format	Lint	Breaking	Updated (UTC)
✅ passed	✅ passed	✅ passed	⏩ skipped	Feb 23, 2025, 7:06 PM

[weeco]

In my opinion using name for obvious cases such as a message already named after this specific resource seems fine. In this PR's case (cloud storage) I agree we should rename it to topic_name, good spot and indeed a good opportunity to ensure consistent naming.