Add Apache 2.0 license

[usmansalimLM]

Licenses this repo and @likeminds.community/feed-rn-core under Apache 2.0.

Replaces #134, which was blocked by the Validate Source Branch Pattern check. The commits
are byte-for-byte identical (tip ecbc3ec); only the branch name changed, from
chore/apache-2.0-license to release/v1.17.2 to satisfy
^release/v[0-9]+\.[0-9]+\.[0-9]+$. No content was rebuilt or re-derived.

Changes

File	Change
LICENSE	new — canonical Apache 2.0 text, repo root
NOTICE	new — LikeMinds copyright attribution (required by Apache §4(d))
likeminds-feed-reactnative-integration/LICENSE	new — same text, so it ships inside the npm tarball
likeminds-feed-reactnative-integration/package.json	"license" changed from ISC to Apache-2.0

Why two LICENSE files

The root LICENSE is what GitHub reads for the repository license badge. But npm packs only the
files inside likeminds-feed-reactnative-integration/, so the root file would not reach npm
consumers. Both are needed and both are byte-identical. Standard practice for a monorepo that
publishes a subdirectory.

The three sample apps are intentionally untouched

qna-feed, social-feed, and social-feed-expo are all marked "private": true and declare no
license field. They are not published to npm and are covered by the root LICENSE. Their
package.json files are unchanged.

The package.json change matters as much as the LICENSE file

npm consumers' license scanners read the registry metadata, not this repo. It takes effect on the
next published version only; 1.17.1 and earlier keep ISC on npm permanently.

This is a relicense from ISC to Apache 2.0. Every contributor to this repo appears to be
LikeMinds staff, so this should be an internal decision, but please confirm before merging.

⚠️ Note on the branch name

The branch is release/v1.17.2 because that is the only naming pattern this repo's CI accepts
besides hotfix/LM-<ticket>_.... The latest tag is v1.17.1 and feed-rn-core is at 1.17.1,
so v1.17.2 is the next patch.

This PR does not bump the package.json version. If your convention is that a
release/vX.Y.Z branch also carries the version bump, add that before merging — note
create-tag-and-release.yml compares package.json against the last tag when manually
dispatched. Worth noting the license metadata only reaches npm on the next publish anyway, so
pairing this with a 1.17.2 release is a sensible way to ship it.

Notes for the reviewer

The LICENSE files are byte-identical to https://www.apache.org/licenses/LICENSE-2.0.txt
(SHA-256 cfc7749b96f63bd31c3c42b5c471bf756814053e847c10f3eb003417bc523d30). Please do not
reformat them or fill in the Copyright [yyyy] [name of copyright owner] placeholder in the
Appendix — that placeholder is part of the Appendix's instructions, not this repo's copyright
notice. Editing the text makes scanners report "Other" instead of "Apache-2.0". The repo's
copyright notice lives in NOTICE.

Context

@likeminds.community/feed-rn-core -> likeminds-feed-reactnative       (this repo, public)
└── @likeminds.community/feed-rn  -> likeminds-feed-reactnative-data  (PRIVATE)
    └── @likeminds.community/feed-js -> likeminds-feed-js-data        (PRIVATE)

Both dependencies are private and must be opened for this SDK to be usable as open source. That
is a separate decision.

Flagged, not changed

This repo has no root README.md and no README in the published package directory, so there is
no ## License section to add. Not created here to avoid inventing project documentation.