feat: add autoware_geography_utils from autoware.universe with history

[xmfcx]

Description

This is a test PR.

• Reference: feat: port autoware_geography_utils from autoware.universe #100 (review)

• Simple version: feat: port autoware_geography_utils from autoware.universe #100

I've ran these commands:

sudo apt update
sudo apt install git-filter-repo

a fresh clone

a@b:~/projects$ git clone https://github.com/autowarefoundation/autoware.universe.git
a@b:~/projects$ cd autoware.universe
a@b:~/projects/autoware.universe$ git filter-repo --path common/autoware_geography_utils
a@b:~/projects/autoware.universe$ git checkout -b feat/add-autoware_geography_utils
a@b:~/projects/autoware.universe$ git remote add core https://github.com/autowarefoundation/autoware.core.git
a@b:~/projects/autoware.universe$ git rebase --root feat/add-autoware_geography_utils --onto core/main

and pushed.

This kept the commits that contributed to this package intact and rebased on top of the main.

How was this PR tested?

Notes for reviewers

None.

Interface changes

None.

Effects on system behavior

None.

[xmfcx]

@youtalk @mitsudome-r

This keeps the commits intact but most of the reasoning is within the actual PR links.

Maybe it's better to have it merged without the history.

Because the history before moving to this repo can be best traversed within the original universe repository.

And the links in the commit titles (like feat!: replace tier4_map_msgs with autoware_map_msgs for MapProjectorInfo (#9392) )
these numbers are large and refer to universe PRs. Won't work from this repository.

I'd prefer to merge as a fresh package like in:

• feat: port autoware_geography_utils from autoware.universe #100

EDIT:
By the way, because the autoware_ prefix task renamed the folder, the git-filter-repo was able to retrieve the history until the refactor operation PR.

[xmfcx]

Also @youtalk -san, I didn't need to use git subtree split while doing this.

Shared my steps in the description above.

Did I achieve the end result you were proposing here?

Commits of this PR: https://github.com/autowarefoundation/autoware.core/pull/103/commits

[youtalk]

@xmfcx I believe that the commit history should still be preserved despite the inconsistencies in links and renaming the package. Since we basically use squash merges, the link issue isn’t much of a problem. I think being able to trace the history from the descriptions of this commit or this PR are valuable.
I think merge commits are better than squash merges in case of these porting PRs but they disrupt the linear history.

Ref.

• feat: import from autoware_common autoware_utils#1 (comment) by @esteve
• feat: import from autoware_common/tmp autoware_lanelet2_extension#1 (comment) by @isamu-takagi

[youtalk]

If we want to maintain the commit history, we’ll need to add a commit to reassign version numbers. This is troublesome. As @xmfcx suggested, copying might be a better option...

[xmfcx]

I’m grateful for your consideration ❤️
The commit history will remain within the Universe repository, so there's no need to duplicate it here.

People can trace back from these PRs back to Universe, that should suffice 👍
And they can make use of the links in the commit messages to the PR's themselves to see the reason why each item was implemented.