Storage API changes with name and field_behavior

[glimchb]

• feat(storage): fill field_behavior for resource name
• feat(storage): fix field numbers
• feat(storage): use name key in statistics
• feat(storage): leftover fixes to fields and numbers
• feat(storage): change from OPTIONAL to OUTPUT_ONLY
• feat(storage): fix AIP core::0127:resource-name-extraction
• feat(storage): fix AIP core::0127::http-annotation
• feat(storage): auto-generate protos
• refactor(storage): add IMMUTABLE behavior for resource name field

see https://google.aip.dev/203

[intelfisz]

@glimchb - please change the commit msgs for fixes to have fix(storage) as prefix

[artek-koltun]

@glimchb - please change the commit msgs for fixes to have fix(storage) as prefix

There are some guidance from angular here. Based on that: feat(storage): fill field_behavior for resource name -> refactor/feat feat(storage): fix field numbers -> fix feat(storage): use name key in statistics -> refactor/feat feat(storage): leftover fixes to fields and numbers -> refactor/feat feat(storage): change from OPTIONAL to OUTPUT_ONLY -> refactor/feat feat(storage): fix AIP core::0127:resource-name-extraction -> ci feat(storage): fix AIP core::0127::http-annotation -> ci feat(storage): auto-generate protos -> chore? it is a special category in Conventional commit but missed in Angular for such housekeeping tasks

[glimchb]

@glimchb - please change the commit msgs for fixes to have fix(storage) as prefix

done, thanks for suggestion