Add brave-ios repo & git history

[kylehickinson]

This adds the contents and git history of https://github.com/brave/brave-ios to the ios/brave-ios directory.

See #21553 for the migration where presubmits/linters are fixed properly

Resolves

Submitter Checklist:

• I confirm that no security/privacy review is needed and no other type of reviews are needed, or that I have requested them
• There is a ticket for my issue
• Used Github auto-closing keywords in the PR description above
• Wrote a good PR/commit description
• Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the repo, not your PR
• Added appropriate labels (QA/Yes or QA/No; release-notes/include or release-notes/exclude; OS/...) to the associated issue
• Checked the PR locally:
  • npm run test -- brave_browser_tests, npm run test -- brave_unit_tests wiki
  • npm run presubmit wiki, npm run gn_check, npm run tslint
• Ran git rebase master (if needed)

Reviewer Checklist:

• A security review is not needed, or a link to one is included in the PR description
• New files have MPL-2.0 license header
• Adequate test coverage exists to prevent regressions
• Major classes, functions and non-trivial code blocks are well-commented
• Changes in component dependencies are properly reflected in gn
• Code follows the style guide
• Test plan is specified in PR before merging

After-merge Checklist:

• The associated issue milestone is set to the smallest version that the
  changes has landed on
• All relevant documentation has been updated, for instance:
  • https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove)
  • https://github.com/brave/brave-browser/wiki/Proxy-redirected-URLs
  • https://github.com/brave/brave-browser/wiki/Fingerprinting-Protections
  • https://github.com/brave/brave-browser/wiki/Brave%E2%80%99s-Use-of-Referral-Codes
  • https://github.com/brave/brave-browser/wiki/Web-Compatibility-Exceptions-in-Brave
  • https://github.com/brave/brave-browser/wiki/QA-Guide
  • https://github.com/brave/brave-browser/wiki/P3A

Test Plan:

[stoletheminerals]

Resolved the rest of the semgrep alerts. Thanks for pinging @thypon

[brave-builds]

A Storybook has been deployed to preview UI for the latest push

[github-actions]

The following commits were not verified:
0b635e7 (unsigned)
746cf97 (unsigned)
cd5ca57 (unsigned)
b913cda (unsigned)
36282c6 (unsigned)
277a138 (unsigned)
97e1adc (unsigned)
7d5c5fd (unsigned)
685d0e6 (unsigned)
6d384a8 (unsigned)
0395845 (unsigned)
a6c20d3 (unsigned)
d9c4513 (unsigned)
a3aea32 (unsigned)
5e77e84 (unsigned)
d8bfac1 (unsigned)
a39ab90 (unsigned)
8b763b2 (unsigned)
d32ddff (unsigned)
6613060 (unsigned)
72fedda (unsigned)
f9c4637 (unsigned)
3802b2e (unsigned)
73d0f28 (unsigned)
c28c7c9 (unsigned)
9993b8f (unsigned)
0082c2f (unsigned)
0c52c94 (unsigned)
5e0c65e (unsigned)
02a6cce (unsigned)

[github-actions]

_{reported by reviewdog 🐶}
[safesvg] element text: validity error : Syntax of value for attribute id of text is not valid

Run SVGO on your assets


Cc @fmarier @thypon

[github-actions]

_{reported by reviewdog 🐶}
[safesvg] element text: validity error : Syntax of value for attribute id of text is not valid

Run SVGO on your assets


Cc @fmarier @thypon

[github-actions]

_{reported by reviewdog 🐶}
[safesvg] element text: validity error : Syntax of value for attribute id of text is not valid

Run SVGO on your assets


Cc @fmarier @thypon

[github-actions]

_{reported by reviewdog 🐶}
[safesvg] element text: validity error : Syntax of value for attribute id of text is not valid

Run SVGO on your assets


Cc @fmarier @thypon

[github-actions]

_{reported by reviewdog 🐶}
[safesvg] element text: validity error : Syntax of value for attribute id of text is not valid

Run SVGO on your assets


Cc @fmarier @thypon

[github-actions]

_{reported by reviewdog 🐶}
[safesvg] element text: validity error : Syntax of value for attribute id of text is not valid

Run SVGO on your assets


Cc @fmarier @thypon

[github-actions]

_{reported by reviewdog 🐶}
[safesvg] element text: validity error : Syntax of value for attribute id of text is not valid

Run SVGO on your assets


Cc @fmarier @thypon

[github-actions]

_{reported by reviewdog 🐶}
[safesvg] element text: validity error : Syntax of value for attribute id of text is not valid

Run SVGO on your assets


Cc @fmarier @thypon

[github-actions]

_{reported by reviewdog 🐶}
[safesvg] element text: validity error : Syntax of value for attribute id of text is not valid

Run SVGO on your assets


Cc @fmarier @thypon

[github-actions]

_{reported by reviewdog 🐶}
[safesvg] element text: validity error : Syntax of value for attribute id of text is not valid

Run SVGO on your assets


Cc @fmarier @thypon

[github-actions]

_{reported by reviewdog 🐶}
[semgrep] Unencrypted request over HTTP detected.

Source: https://semgrep.dev/r/typescript.react.security.react-insecure-request.react-insecure-request


Cc @fmarier @thypon

[github-actions]

_{reported by reviewdog 🐶}
[semgrep] A gitleaks hashicorp-tf-password was detected which attempts to identify hard-coded credentials. It is not recommended to store credentials in source-code, as this risks secrets being leaked and used by either an internal or external malicious adversary. It is recommended to use environment variables to securely provide credentials or retrieve credentials from a secure vault or HSM (Hardware Security Module).

Source: https://semgrep.dev/r/generic.secrets.gitleaks.hashicorp-tf-password.hashicorp-tf-password


Cc @fmarier @thypon

[github-actions]

_{reported by reviewdog 🐶}
[semgrep] A gitleaks hashicorp-tf-password was detected which attempts to identify hard-coded credentials. It is not recommended to store credentials in source-code, as this risks secrets being leaked and used by either an internal or external malicious adversary. It is recommended to use environment variables to securely provide credentials or retrieve credentials from a secure vault or HSM (Hardware Security Module).

Source: https://semgrep.dev/r/generic.secrets.gitleaks.hashicorp-tf-password.hashicorp-tf-password


Cc @fmarier @thypon

[github-actions]

_{reported by reviewdog 🐶}
[semgrep] A gitleaks hashicorp-tf-password was detected which attempts to identify hard-coded credentials. It is not recommended to store credentials in source-code, as this risks secrets being leaked and used by either an internal or external malicious adversary. It is recommended to use environment variables to securely provide credentials or retrieve credentials from a secure vault or HSM (Hardware Security Module).

Source: https://semgrep.dev/r/generic.secrets.gitleaks.hashicorp-tf-password.hashicorp-tf-password


Cc @fmarier @thypon

[github-actions]

_{reported by reviewdog 🐶}
[semgrep] A gitleaks hashicorp-tf-password was detected which attempts to identify hard-coded credentials. It is not recommended to store credentials in source-code, as this risks secrets being leaked and used by either an internal or external malicious adversary. It is recommended to use environment variables to securely provide credentials or retrieve credentials from a secure vault or HSM (Hardware Security Module).

Source: https://semgrep.dev/r/generic.secrets.gitleaks.hashicorp-tf-password.hashicorp-tf-password


Cc @fmarier @thypon

[github-actions]

_{reported by reviewdog 🐶}
[semgrep] A gitleaks hashicorp-tf-password was detected which attempts to identify hard-coded credentials. It is not recommended to store credentials in source-code, as this risks secrets being leaked and used by either an internal or external malicious adversary. It is recommended to use environment variables to securely provide credentials or retrieve credentials from a secure vault or HSM (Hardware Security Module).

Source: https://semgrep.dev/r/generic.secrets.gitleaks.hashicorp-tf-password.hashicorp-tf-password


Cc @fmarier @thypon

[github-actions]

_{reported by reviewdog 🐶}
[semgrep] A gitleaks hashicorp-tf-password was detected which attempts to identify hard-coded credentials. It is not recommended to store credentials in source-code, as this risks secrets being leaked and used by either an internal or external malicious adversary. It is recommended to use environment variables to securely provide credentials or retrieve credentials from a secure vault or HSM (Hardware Security Module).

Source: https://semgrep.dev/r/generic.secrets.gitleaks.hashicorp-tf-password.hashicorp-tf-password


Cc @fmarier @thypon

[github-actions]

_{reported by reviewdog 🐶}
[semgrep] A gitleaks hashicorp-tf-password was detected which attempts to identify hard-coded credentials. It is not recommended to store credentials in source-code, as this risks secrets being leaked and used by either an internal or external malicious adversary. It is recommended to use environment variables to securely provide credentials or retrieve credentials from a secure vault or HSM (Hardware Security Module).

Source: https://semgrep.dev/r/generic.secrets.gitleaks.hashicorp-tf-password.hashicorp-tf-password


Cc @fmarier @thypon

[github-actions]

_{reported by reviewdog 🐶}
[semgrep] A gitleaks hashicorp-tf-password was detected which attempts to identify hard-coded credentials. It is not recommended to store credentials in source-code, as this risks secrets being leaked and used by either an internal or external malicious adversary. It is recommended to use environment variables to securely provide credentials or retrieve credentials from a secure vault or HSM (Hardware Security Module).

Source: https://semgrep.dev/r/generic.secrets.gitleaks.hashicorp-tf-password.hashicorp-tf-password


Cc @fmarier @thypon

[github-actions]

_{reported by reviewdog 🐶}
[semgrep] A gitleaks hashicorp-tf-password was detected which attempts to identify hard-coded credentials. It is not recommended to store credentials in source-code, as this risks secrets being leaked and used by either an internal or external malicious adversary. It is recommended to use environment variables to securely provide credentials or retrieve credentials from a secure vault or HSM (Hardware Security Module).

Source: https://semgrep.dev/r/generic.secrets.gitleaks.hashicorp-tf-password.hashicorp-tf-password


Cc @fmarier @thypon

[brave-builds]

A Storybook has been deployed to preview UI for the latest push