chore(i18n): add samoan locale

[DrewShirts]

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Chore: This PR adds the Samoan locale file for ngLocale.

What is the current behavior? (You can also link to an open issue here)
There currently is not a locale file for Samoan in ngLocale.
#7246

What is the new behavior (if this is a feature change)?
This adds the ability to translate content to Samoan.

Does this PR introduce a breaking change?
No.

Please check if the PR fulfills these requirements

• The commit message follows our guidelines
• Fix/Feature: Docs have been added/updated
• Fix/Feature: Tests have been added; existing tests pass
  Other information:
  No tests are available: See angular.js issue 7246: No unit tests for ngLocale #7246
  This was copied and then adapted from angular/bower-angular-i18n (originally committed by @spiffy2man: Added file for Samoan language translations. bower-angular-i18n#26).

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[DrewShirts]

I signed the cla.

[googlebot]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and have the pull request author add another comment and the bot will run again. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

[googlebot]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and have the pull request author add another comment and the bot will run again. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

[Narretz]

Thanks for the PR. However since we are in Long Term Stability mode we are not going to add new locales to AngularJS.

[DrewShirts]

Thanks for the PR. However since we are in Long Term Stability mode we are not going to add new locales to AngularJS.

@Narretz, I can understand that. How long will this have to wait until we can add the Samoan locale to angular.js? Can this be scheduled for when it will be an approvable PR?

[Narretz]

Sorry if I wasn't clear, but feature development for AngularJS is completely over. We advise everyone to use the new Angular: https://angular.io/
However, with i18n you can simply take the Samoan ngLocale module you created and add it to your application without it being in an official release.

[DrewShirts]

Sorry if I wasn't clear, but feature development for AngularJS is completely over. We advise everyone to use the new Angular: https://angular.io/
However, with i18n you can simply take the Samoan ngLocale module you created and add it to your application without it being in an official release.

Sounds good. Will do.