PDX-19: Add UnloadFromGarages Action

[XxshiftxX]

Add UnloadFromGarages action with data structure and serialize/deserialize code.
Implementation of execution will be added following PR.

[pull-request-quantifier-deprecated]

This PR has 184 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Medium
Size       : +184 -0
Percentile : 56.8%

Total files changed: 3

Change summary by file extension:
.cs : +184 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

[moreal]

It is too sad to duplicate codes for type because of csharplang's limitation. 😢

[XxshiftxX]

type Foo = (...)

😢

[moreal]

It will be treated as null instead of throwing an error, even if invalid items like Dictionary became.

[moreal]

Also, we should consider unload_from_garages as good naming 🤔 Should it be bulk_unload_from_my_garages? 🤔 @boscohyun Please leave your opinion 🙏🏻

[boscohyun]

Also, we should consider unload_from_garages as good naming 🤔 Should it be bulk_unload_from_my_garages? 🤔 @boscohyun Please leave your opinion 🙏🏻

Thanks for mentioning me.

1. It's OK to remove my from action identifier. Because the action use signer address basically.
2. Choosing to add bulk to the action identifier is easy and reasonable.

[XxshiftxX]

Also, we should consider unload_from_garages as good naming 🤔 Should it be bulk_unload_from_my_garages? 🤔 @boscohyun Please leave your opinion 🙏🏻

Thanks for mentioning me.

1. It's OK to remove my from action identifier. Because the action use signer address basically.
2. Choosing to add bulk to the action identifier is easy and reasonable.

@boscohyun @moreal Thank you for your opinion. I think build_unload_from_garages is nice option to represent how it works.
It seems to hard to change names now because it has many following PR/branches. So I'll apply this after bunch of branches merge into a single branch so that there's no remaining branch dependency.