Added @UsesFeatures annotation

[jewelshkjony]

General items:

• I have updated the relevant documentation files under docs/
• My code follows the:
  • Google Java style guide (for .java files)
  • Google JavaScript style guide (for .js files)
• ant tests passes on my machine

If your code changes how something works on the device (i.e., it affects the companion):

• I branched from ucr
• My pull request has ucr as the base

Further, if you've changed the blocks language or another user-facing designer/blocks API (added a SimpleProperty, etc.):

• I have updated the corresponding version number in appinventor/components/src/.../common/YaVersion.java
• I have updated the corresponding upgrader in appinventor/appengine/src/.../client/youngandroid/YoungAndroidFormUpgrader.java (components only)
• I have updated the corresponding entries in appinventor/blocklyeditor/src/versioning.js

For all other changes:

• I branched from master
• My pull request has master as the base

What does this PR accomplish?

Added the ability to declare <uses-feature> element in AndroidManifest.xml.

Example usage # .

@UsesFeatures(features = {
  @FeatureElement(name = "android.hardware.bluetooth", required = false),
  @FeatureElement(name = "android.hardware.wifi", required = true),
  @FeatureElement(name = "android.hardware.camera", required = false)
})

Resolves # .

[AppInventorWorkerBee]

Can one of the admins verify this patch?

[AppInventorWorkerBee]

Can one of the admins verify this patch?

[jewelshkjony]

@AppInventorWorkerBee ok to test

[ewpatton]

@AppInventorWorkerBee ok to test

[jewelshkjony]

I tested with a dummy extension that has duplicate @UsesFeatures. And now it is successfully resolving duplicates by taking only the required one.

[ewpatton]

One minor change, otherwise LGTM.

[ewpatton]

I had another thought, and this would be a breaking change so we may want it as a separate PR... but we may want to add the @UsesFeatures annotations to the appropriate core components and remove the code that unconditionally adds them in the CreateManifest build task. For example, an app that does drawing on a canvas won't need to declare Bluetooth as a feature but currently it does.