Consider disabling field alignment lint check

[andrewsykim]

We initially enabled field alignment lint for memory optimization. However, I find that force reordering fields often come at a cost of readability and is adding more friction in development compared to the performance improvements we get from it.

For example, this was a recent lint failure for a unit test that I thought was unecessary:

Opening this issue to get thoughts from other contributors

[andrewsykim]

@rueian @Future-Outlier thoughts?

[rueian]

👍

[Future-Outlier]

+1 on disabling this.
my points:

1. readability > memory optimization (in this project)
2. The Go team themselves removed the fieldalignment analyzer from gopls in v0.17.0. Alan Donovan (gopls maintainer) noted that its false positive rate is almost 100% and proposed deleting it altogether: x/tools/gopls: fieldalignment analyzer reports confusing "errors" about memory layout golang/go#67762 (comment)

[jinbum-kim]

Hello, it looks like fieldalignment is enabled explicitly in .golangci.yml here:

kuberay/.golangci.yml

Lines 36 to 38 in 94c85c2

	govet:
	enable:
	- fieldalignment

Is removing this entry the preferred way to disable it? If yes, I can open a PR.

[andrewsykim]

@jinbum-kim yes, please open a PR, thank you!